| 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: <20090804105004.GA4016@gradator.net>
Date: Tue, 4 Aug 2009 12:50:04 +0200
From: Sylvain Rochet <gradator@...dator.net>
To: "J. Bruce Fields" <bfields@...ldses.org>
Cc: Jan Kara <jack@...e.cz>, linux-kernel@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-nfs@...r.kernel.org
Subject: Re: 2.6.28.9: EXT3/NFS inodes corruption
Hi,
On Tue, Jul 28, 2009 at 05:12:15PM -0400, J. Bruce Fields wrote:
> On Tue, Jul 28, 2009 at 06:41:42PM +0200, Sylvain Rochet wrote:
> >
> > [...]
> > May 26 12:34:39 cognac kernel: NFS: Buggy server - nlink == 0!
> > May 26 12:39:43 cognac kernel: NFS: Buggy server - nlink == 0!
> >
> > This is obviously related to the corruption.
>
> It might be interesting to know whether the file that we returned to the
> client with nlink 0 was the same that you later saw corruption on; maybe
> adding a printk of the inode number there would help.
>
> Googling around on that error message, a previous thread:
>
> http://marc.info/?t=107429333300004&r=1&w=4
>
> seems to conclude it's a bug, but doesn't followup with a fix. And I
> don't see any mention of possible filesystem corruption.
>
> Is NFSv4 involved here? I wonder if something that might otherwise be
> only a problem for the client could become a problem for the server if
> it attempts to do further operations with an unlinked inode in a
> compound operation that follows a lookup.
NFSv3 here.
Sylvain
Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)
Powered by blists - more mailing lists