| 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: Wed, 12 Mar 2008 14:08:03 -0400 From: Trond Myklebust <Trond.Myklebust@...app.com> To: Adam Schrotenboer <adam@...00.com> Cc: Neil Brown <neilb@...e.de>, linux-kernel@...r.kernel.org, linux-nfs@...r.kernel.org, Thomas Daniel <tdaniel@...00.com>, jesper.juhl@...il.com, Fred Revenu <frevenu@...00.com> Subject: Re: [opensuse] nfs_update_inode: inode X mode changed, Y to Z On Wed, 2008-03-12 at 10:55 -0700, Adam Schrotenboer wrote: > Another excerpt from last night. > > Mar 12 00:53:16 wanda kernel: nfs: server 192.168.1.27 not responding, > still trying > Mar 12 00:53:18 wanda kernel: nfs: server 192.168.1.27 OK > Mar 12 00:54:29 wanda kernel: nfs_update_inode: inode 1075049148 mode > changed, 0040755 to 0100644 Hang on. That does not look like an XID collision problem... That code path basically means that the fileids/inode numbers match, which would not be the case if we were talking about an XID collision causing the reply cache to replay an old request... That message rather symptomatic of a filehandle reuse problem. In other words a NFS filehandle appears to be reused to label a regular file after it has been used for a directory with the same fileid/inode number. That is a definite server bug. Are you sure that you are using the regular kernel nfs server? -- Trond Myklebust NFS client maintainer NetApp Trond.Myklebust@...app.com www.netapp.com -- 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