| 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: <5065A456.4070007@netapp.com> Date: Fri, 28 Sep 2012 09:21:26 -0400 From: Bryan Schumaker <bjschuma@...app.com> To: Joerg Roedel <joro@...tes.org> CC: Joerg Roedel <joerg.roedel@....com>, "Myklebust, Trond" <Trond.Myklebust@...app.com>, "linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org> Subject: Re: kernel BUG at /data/lemmy/linux.trees.git/fs/nfs/idmap.c:681! On 09/28/2012 08:17 AM, Joerg Roedel wrote: > On Thu, Sep 27, 2012 at 02:15:21PM -0400, Bryan Schumaker wrote: > >> Double check that you're using the legacy idmapper, and not the >> keyring based one (/etc/request-key.conf shouldn't have the "create >> id_resolver * * /usr/bin/nfsidmap %k %d" line). > > That should only be relevant for NFSv4, no? I am using v3 only (without > explicitly setting the version as mount option). Any idmapper problem is only relevant to v4, so if you're seeing a problem that means you're not using NFS v3. > > Anyway, I had no luck on reproducing the failure again after > re-installation of the box, either with of with-out my patches on-top. I > tried a few different config settings for NFS too, but the BUG didn't > trigger again :-/ Maybe it's mounting over v3 now? Can you retry using "vers=4" in your mount options? - Bryan > > > 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