lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 08 Apr 2010 10:48:01 +0300 From: Timo Teräs <timo.teras@....fi> To: Stephen Rothwell <sfr@...b.auug.org.au> CC: David Miller <davem@...emloft.net>, netdev@...r.kernel.org, linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org> Subject: Re: linux-next: powerpc boot failure Stephen Rothwell wrote: > Hi, > > On Thu, 08 Apr 2010 10:29:49 +0300 Timo Teräs <timo.teras@....fi> wrote: >> You don't probably have any xfrm policies then. And that code should not >> really get executed. >> >> Some of the changes touch globally visible structs, and inline functions. >> Was this a clean rebuild? And did you update all kernel modules, also in >> the initramfs? > > Yes, the build is started from scratch and the kernel and modules are > updated (this is our automated build and test system). > > I have attached the config in case that is of use. Thanks, I'll check some of the xfrm related configs. Can you on running system do: ip xfrm policy That shows if there's any policies due to e.g. ipsec or tcp-md5. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists