| 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: <200610171250.56522.ak@suse.de> Date: Tue, 17 Oct 2006 12:50:56 +0200 From: Andi Kleen <ak@...e.de> To: Ian Kent <raven@...maw.net> Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org Subject: Re: BUG dcache.c:613 during autofs unmounting in 2.6.19rc2 On Tuesday 17 October 2006 06:15, Ian Kent wrote: > On Mon, 2006-10-16 at 16:58 +0200, Andi Kleen wrote: > > While unmounting autofs on shutdown my workstation got a dcache.c:613 BUG > > with 2.6.19rc2. > > > > Only jpegs available unfortunately: > > > > http://one.firstfloor.org/~andi/autofs-oops1.jpg > > http://one.firstfloor.org/~andi/autofs-oops2.jpg > > > > I think it was autofs3 instead of autofs4 - at least I got both compiled in. > > The autofs user land was autofs-4.1.4 (-6 suse rpm) > > Don't think compiling both in is a good idea. > They both register as "autofs" so you really should choose one and > disable the other. > > For my part I have to recommend autofs4 (personally I'd like to see the > autofs v3 module deprecated) and autofs4 is really needed if your using > autofs version 4 or above. Well it always worked this way in earlier kernels and even if the wrong module was suddenly used for some reason it shouldn't BUG. So something is broken. -Andi - 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