| 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
| ||
|
Message-ID: <20060824165534.A3003989@wobbly.melbourne.sgi.com> Date: Thu, 24 Aug 2006 16:55:34 +1000 From: Nathan Scott <nathans@....com> To: Paul Slootman <paul+nospam@...tel.net> Cc: linux-kernel@...r.kernel.org Subject: Re: 2.6.18-rc3-git3 - XFS - BUG: unable to handle kernel NULL pointer dereference at virtual address 00000078 On Wed, Aug 23, 2006 at 10:42:10AM +0200, Paul Slootman wrote: > > I compiled 2.6.17.9 yesterday with gcc 4.1 (the previous kernel that > showed problems was 2.6.17.7 compiled with gcc 3.3.5), and the same > problem showed itself again, after 2.6.15.6 had run with no problems > whatsoever for 5 days. > > I'll now give 2.6.16.1 a go (we have that kernel lying around :-) Hmm, if there's no reproducible case, next best thing is a git bisect to try to identify potential commits which are causing the problem... not easy on your production server, I know. I had believed this to be a long-standing issue though, I'm sure I've seen it reported before - we've never had any information to go on to try to diagnose it however. Jesper's rename hint is the most helpful information we've had so far. > BTW, what's the significance of the xfs_repair message > LEAFN node level is 1 inode 827198 bno = 8388608 > (I see a lot more of these this time round). It basically means a directory inode's btree has got into an invalid state, somehow. cheers. -- Nathan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists