Beware, ZFS on head!
Depending on how you build it, you may either get a kernel compile failure (if you build zfs into the core kernel with options ZFS), or possibly even an invalid zfs.ko with an undefined symbol that can't be used at reboot time. Be exceptionally careful. I suggest, before rebooting, do a # nm /boot/kernel/zfs.ko | grep atomic_dec If you see: U atomic_dec_64_nv .. you will have a sub-optimal reboot experience and you may want to save your kernel.old. (no output = you're fine = carry on!) -- Peter Wemm - pe...@wemm.org; pe...@freebsd.org; pe...@yahoo-inc.com; KI6FJV UTF-8: for when a ' or ... just won\342\200\231t do\342\200\246 signature.asc Description: This is a digitally signed message part.
Re: [CFT] SSP Package Repository available
Bryan Drewery wrote: Ports now support enabling Stack Protector [1] support on FreeBSD 10 i386 and amd64, and older releases on amd64 only currently. Support may be added for earlier i386 releases once all ports properly respect LDFLAGS. To enable, just add WITH_SSP=yes to your make.conf and rebuild all ports. The default SSP_CLFAGS is -fstack-protector, but -fstack-protector-all may optionally be set instead. That's probably SSP_CFLAGS, not SSP_CLFAGS. Does clang (in 10-STABLE or CURRENT) support also the option -fstack-protector-strong ? Is 'world' by default compiled with -fstack-protector (and if not, why not). Mark ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFT] SSP Package Repository available
On 8/21/2014 5:34 AM, Mark Martinec wrote: Bryan Drewery wrote: Ports now support enabling Stack Protector [1] support on FreeBSD 10 i386 and amd64, and older releases on amd64 only currently. Support may be added for earlier i386 releases once all ports properly respect LDFLAGS. To enable, just add WITH_SSP=yes to your make.conf and rebuild all ports. The default SSP_CLFAGS is -fstack-protector, but -fstack-protector-all may optionally be set instead. That's probably SSP_CFLAGS, not SSP_CLFAGS. Nice find. Does clang (in 10-STABLE or CURRENT) support also the option -fstack-protector-strong ? Not sure if clang 3.4 has it, but I found a patch for it here: https://github.com/archlinuxarm/PKGBUILDs/blob/master/extra/llvm/clang-3.4-fstack-protector-strong.patch Is 'world' by default compiled with -fstack-protector (and if not, why not). World has been built with -fstack-protector by default since 2008. At least in 8.0+. Mark ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: [CFT] SSP Package Repository available
On 8/21/2014 10:53 AM, Bryan Drewery wrote: On 8/21/2014 5:34 AM, Mark Martinec wrote: Bryan Drewery wrote: Ports now support enabling Stack Protector [1] support on FreeBSD 10 i386 and amd64, and older releases on amd64 only currently. Support may be added for earlier i386 releases once all ports properly respect LDFLAGS. To enable, just add WITH_SSP=yes to your make.conf and rebuild all ports. The default SSP_CLFAGS is -fstack-protector, but -fstack-protector-all may optionally be set instead. That's probably SSP_CFLAGS, not SSP_CLFAGS. Nice find. Does clang (in 10-STABLE or CURRENT) support also the option -fstack-protector-strong ? Not sure if clang 3.4 has it, but I found a patch for it here: I'm told that clang 3.5 has support for it. We do not (yet) have 3.5 in CURRENT. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
r270287: crash
FreeBSD r270287 crashes/reboots instantanously on loading the kernel. I can not see at what point (on modern systems like Ivy Bridge). On older Core2Duo systems I get a trap 12 in APIC or similar. While I was able to start kernel.old on the modern systems, I fail on both kernel and kernel.old on the C2D system. I'd like to know whether there is a way to save the system I can not reboot the on-disk kernels snce they are, woderfull, compromised. Is there a possible scenario like: a) boot from DVD ROM or USB most recent snapshot b) establish network with on-disk config, svn checkout recent sources into on-disk file hierarchy c) build repaired/patched kernel and install on on-disk (not on the emergency boot media). Thanks, help appreciated and what is about this crash affecting recent CURRENT r270287, what has corrupted the system? Regards, Oliver signature.asc Description: PGP signature
Re: r270287: crash
On Aug 21, 2014, at 12:26 PM, O. Hartmann ohart...@zedat.fu-berlin.de wrote: FreeBSD r270287 crashes/reboots instantanously on loading the kernel. I can not see at what point (on modern systems like Ivy Bridge). On older Core2Duo systems I get a trap 12 in APIC or similar. While I was able to start kernel.old on the modern systems, I fail on both kernel and kernel.old on the C2D system. I'd like to know whether there is a way to save the system I can not reboot the on-disk kernels snce they are, woderfull, compromised. Is there a possible scenario like: a) boot from DVD ROM or USB most recent snapshot b) establish network with on-disk config, svn checkout recent sources into on-disk file hierarchy c) build repaired/patched kernel and install on on-disk (not on the emergency boot media). I would grab a snapshot ISO or USB disk image: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/ISO-IMAGES/11.0/ . After that you can mount your filesystems, revert to an earlier SVN revision, and repair your system that way. You could also copy over the /boot/kernel as long as you didn’t have/need any customizations. Thanks, help appreciated and what is about this crash affecting recent CURRENT r270287, what has corrupted the system? That’s a better question. Booting off newer sources worked on my VM at least, but it’s not real hardware. Maybe something dealing with vt(4)/xen? HTH! -Garrett signature.asc Description: Message signed with OpenPGP using GPGMail
Re: r270287: crash
On Thu, Aug 21, 2014 at 12:32 PM, yaneurab...@gmail.com wrote: On Aug 21, 2014, at 12:26 PM, O. Hartmann ohart...@zedat.fu-berlin.de wrote: FreeBSD r270287 crashes/reboots instantanously on loading the kernel. I can not see at what point (on modern systems like Ivy Bridge). On older Core2Duo systems I get a trap 12 in APIC or similar. While I was able to start kernel.old on the modern systems, I fail on both kernel and kernel.old on the C2D system. I'd like to know whether there is a way to save the system I can not reboot the on-disk kernels snce they are, woderfull, compromised. Is there a possible scenario like: a) boot from DVD ROM or USB most recent snapshot b) establish network with on-disk config, svn checkout recent sources into on-disk file hierarchy c) build repaired/patched kernel and install on on-disk (not on the emergency boot media). I would grab a snapshot ISO or USB disk image: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/ISO-IMAGES/11.0/ . After that you can mount your filesystems, revert to an earlier SVN revision, and repair your system that way. You could also copy over the /boot/kernel as long as you didn’t have/need any customizations. Thanks, help appreciated and what is about this crash affecting recent CURRENT r270287, what has corrupted the system? That’s a better question. Booting off newer sources worked on my VM at least, but it’s not real hardware. Maybe something dealing with vt(4)/xen? One important note is that my CURRENT VM on my Macbook runs i386, not amd64. Cheers, -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
