Re: nullfs changes MFC
on 08/12/2012 05:06 Konstantin Belousov said the following: > On Sat, Dec 08, 2012 at 03:58:16AM +0100, Baptiste Daroussin wrote: >> On Sat, Dec 08, 2012 at 03:01:09AM +0200, Konstantin Belousov wrote: > ... >>> The merge is available at >>> http://people.freebsd.org/~kib/misc/nullfs_9.1.patch >> >> >> Sorry I haven't checked the latest zfs related MFC, but for some time >> there was an issue with nullfs improvements and zfs, will this mfc be >> synchronize with the mfc of the related zfs fixes? > > Corresponding zfs fixes were already merged to stable/9, as I was told. > Cc:ed Andrey to confirm it once more. Yes, a while ago. -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Quarantine Digest
Quarantine Digest for freebsd-stable@freebsd.org [1]Click here to access your spam quarantine. The spam quarantine contains emails that are being held from your email account. Quarantined emails can be released to your inbox or deleted using the spam quarantine link. References 1. https://70.46.100.174:8088/quarantine/manageuser?tkn=ZW1tYXsDP%2FiRlcl0JEkbSdMgpozsvxQGIdspVn7AYRfyV0nU&action=viewibx ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Error in openssl for buildworld
Hi all Just tried to buildworld with the 9_1 sources updated today by svn and get this error, both on amd64 and i386: /usr/src_fbsd9/ is on a read-only nfs mount, /usr/obj is local make command was very simple: sudo make buildworld === cc -O2 -pipe -DTERMIOS -DANSI_SOURCE -I/usr/src_fbsd9/secure/lib/libssl/../../../crypto/openssl -I/usr/src_fbsd9/secure/lib/libssl/../../../crypto/openssl/crypto -I/usr/obj/usr/src_fbsd9/secure/lib/libssl -DOPENSSL_THREADS -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_NO_IDEA -DL_ENDIAN -DNO_IDEA -std=gnu99 -fstack-protector -Wno-pointer-sign -c /usr/src_fbsd9/secure/lib/libssl/../../../crypto/openssl/ssl/d1_clnt.c -o d1_clnt.o cc -O2 -pipe -DTERMIOS -DANSI_SOURCE -I/usr/src_fbsd9/secure/lib/libssl/../../../crypto/openssl -I/usr/src_fbsd9/secure/lib/libssl/../../../crypto/openssl/crypto -I/usr/obj/usr/src_fbsd9/secure/lib/libssl -DOPENSSL_THREADS -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_NO_IDEA -DL_ENDIAN -DNO_IDEA -std=gnu99 -fstack-protector -Wno-pointer-sign -c /usr/src_fbsd9/secure/lib/libssl/../../../crypto/openssl/ssl/d1_lib.c -o d1_lib.o /usr/src_fbsd9/secure/lib/libssl/../../../crypto/openssl/ssl/d1_lib.c: In function 'dtls1_check_timeout_num': /usr/src_fbsd9/secure/lib/libssl/../../../crypto/openssl/ssl/d1_lib.c:445: error: 'SSL_F_DTLS1_CHECK_TIMEOUT_NUM' undeclared (first use in this function) /usr/src_fbsd9/secure/lib/libssl/../../../crypto/openssl/ssl/d1_lib.c:445: error: (Each undeclared identifier is reported only once /usr/src_fbsd9/secure/lib/libssl/../../../crypto/openssl/ssl/d1_lib.c:445: error: for each function it appears in.) *** Error code 1 Stop in /usr/src_fbsd9/secure/lib/libssl. *** Error code 1 Stop in /usr/src_fbsd9. *** Error code 1 Stop in /usr/src_fbsd9. *** Error code 1 Stop in /usr/src_fbsd9. *** Error code 1 Stop in /usr/src_fbsd9. === Here is my make.conf: WRKDIRPREFIX=/usr/tmp NOI4B=1 WITH_GECKO=libxul SUP_UPDATE=1 SUP=/usr/bin/csup SUPFLAGS=-L 1 -l /var/run/csup.lock SUPHOST=cvsup.ch.FreeBSD.org SUPFILE=/usr/local/etc/standard-supfile PORTSSUPFILE=/usr/local/etc/ports-supfile WITH_VIM_OPTIONS="YES" WITHOUT_PKGNG=yes # added by use.perl 2012-11-03 10:25:58 PERL_VERSION=5.14.2 and src.conf: WITHOUT_CVS=YES WITHOUT_KERNEL_SYMBOLS=YES I got the same error about 3 weeks ago but put it down to an rc1/2/3 error at the time but according to UPDATING this is 9.1 release code: UPDATING: Updating Information for FreeBSD current users This file is maintained and copyrighted by M. Warner Losh . See end of file for further details. For commonly done items, please see the COMMON ITEMS: section later in the file. These instructions assume that you basically know what you are doing. If not, then please consult the FreeBSD handbook. Items affecting the ports and packages system can be found in /usr/ports/UPDATING. Please read that file before running portupgrade. 20121205: 9.1-RELEASE. I'd appreciate any hints as to what is going wrong. Regards Simon. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: nullfs changes MFC
On Sat, Dec 08, 2012 at 12:35:42PM +0200, Andriy Gapon wrote: > on 08/12/2012 05:06 Konstantin Belousov said the following: > > On Sat, Dec 08, 2012 at 03:58:16AM +0100, Baptiste Daroussin wrote: > >> On Sat, Dec 08, 2012 at 03:01:09AM +0200, Konstantin Belousov wrote: > > ... > >>> The merge is available at > >>> http://people.freebsd.org/~kib/misc/nullfs_9.1.patch > >> > >> > >> Sorry I haven't checked the latest zfs related MFC, but for some time > >> there was an issue with nullfs improvements and zfs, will this mfc be > >> synchronize with the mfc of the related zfs fixes? > > > > Corresponding zfs fixes were already merged to stable/9, as I was told. > > Cc:ed Andrey to confirm it once more. > > Yes, a while ago. > Perfect thank you both! And sorry for noise :) regards, Bapt pgpbYLSRsMLFP.pgp Description: PGP signature
Re: nullfs changes MFC
By combining vop_settext/unset/get into a single call with parameters "op" and &out (for gettext) you can reduce 3 new vops into a single vop. The same can be done for write count vops. This will allow you to preserve kbi by reducing the vop additions to 2. Sent from my iPhone On Dec 7, 2012, at 5:01 PM, Konstantin Belousov wrote: > Hi, > I am going to merge latest batch of the nullfs improvements into > stable/9. This will bring up significant performance enchancements due > to use of the shared locks for lookups if the lower layer supports it, > much better caching on the nullfs layer, and proper handling of the text > segments on the nullfs. Also, it should improve the error recovery and > some corner cases with locking. > > Unfortunately, the merge would break KBI for VFS, since it needs 5 new > VOP slots, and only three spares are left. We already are very liberal > with the VFS KBI, so I do not feel that the merge is not acceptable, due > to the benefits it brings to the nullfs. > > The merge is available at > http://people.freebsd.org/~kib/misc/nullfs_9.1.patch ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Will we get a RELEASE-9.1 for Christmas?
Just checking in, yet again, to ask about the status of FreeBSD 9.1. We've been delaying construction of new servers (which we wanted to build during the US Thanksgiving holiday) until the release, and really want to be able to work on them over Christmas. I understand that the release was held back by server security issues and possibly by problems with CLANG's failure to emulate obscure quirks of GCC; are these now resolved? Is there anything else on the "TODO" list (the version on the Wiki is of no help; it's woefully out of date) to be done prior to release? Does the FreeBSD project need a fresh server to be donated to handle the release? --Brett Glass ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Will we get a RELEASE-9.1 for Christmas?
It's still progressing, albeit slowly. There's been a lot of security checking going on in the background as part of this task and that takes time. Adrian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Will we get a RELEASE-9.1 for Christmas?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It will be released when it is ready. On 12/8/2012 9:18 PM, Brett Glass wrote: > Just checking in, yet again, to ask about the status of FreeBSD > 9.1. We've been delaying construction of new servers (which we > wanted to build during the US Thanksgiving holiday) until the > release, and really want to be able to work on them over Christmas. > I understand that the release was held back by server security > issues and possibly by problems with CLANG's failure to emulate > obscure quirks of GCC; are these now resolved? Is there anything > else on the "TODO" list (the version on the Wiki is of no help; > it's woefully out of date) to be done prior to release? Does the > FreeBSD project need a fresh server to be donated to handle the > release? > > --Brett Glass > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable To > unsubscribe, send any mail to > "freebsd-stable-unsubscr...@freebsd.org" -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJQxBL1AAoJEAGnn5Nn8qWUrPAH/2cgbQ3BYL+E6B1C0Vce0XNY Yxf7IQByzLCsmdXJW62OZoXkOvS1RV/bPFqqiOtd/Vl6v7eaxQgXmXTZuf401eRD FHz2/j9j0BouVnU2nOwcrQxrjB5phjqpAe/87MWrqR2/bQFt3/b7x5EC/oB1hKJ6 5S5A0/Yukh//gpaA5LcMxLZuus3xmRKA7zUugiYi9x8eis+pNu/7n470nnKtZKkZ pRvGxr4F/olUqj0yOw/Pqap9a41Xc4R8L1MjZfbu2fs5ob60qPMva00WEhBgOKQy xfkLFU7hHj+KaZ3AqdoHQbmsiKrMjjK/q1aeibS8nEDMB+RF8T8xoCd33P33960= =aroh -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
