| 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: <50213076.7060003@netapp.com> Date: Tue, 07 Aug 2012 11:12:54 -0400 From: Bryan Schumaker <bjschuma@...app.com> To: Joerg Roedel <joro@...tes.org> CC: Joerg Roedel <joerg.roedel@....com>, Trond Myklebust <Trond.Myklebust@...app.com>, linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org, wdauchy@...il.com Subject: Re: kernel BUG at /data/lemmy/linux.trees.git/fs/nfs/idmap.c:681! On 08/07/2012 10:50 AM, Joerg Roedel wrote: > On Tue, Aug 07, 2012 at 10:36:31AM -0400, Bryan Schumaker wrote: >> Your stack trace is showing v4 calls on the failing box, those >> definitely shouldn't be happening if you're using v3. Can you double >> check /etc/fstab and /proc/mounts on a working kernel to be sure? > > So the bug is probably (for whatever reason) that the nfs4 path is > called for an nfs3 mount :) That's what I'm thinking. If you're not using v4, what happens if you turn CONFIG_NFS_V4 off in your .config for the broken machine? I still haven't been able to trigger the bug, even with your .config, so I'm going to keep poking at it. - Bryan > Anyway, I attach /proc/mounts and /etc/fstab from that box running a > v3.5-rc5 kernel (where it works). Thanks. I don't see anything weird in there. You're using the same settings for the other machine, too? > > > Joerg > -- 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