linux-kernel - Re: 2.6.21-git10/11: files getting truncated on xfs? or maybe an nlink problem?

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <46439491.9010604@goop.org>
Date:	Thu, 10 May 2007 14:54:25 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Chuck Ebbert <cebbert@...hat.com>
CC:	David Chinner <dgc@....com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Matt Mackall <mpm@...enic.com>, xfs@....sgi.com
Subject: Re: 2.6.21-git10/11: files getting truncated on xfs? or maybe an
 nlink problem?

Chuck Ebbert wrote:
> Jeremy Fitzhardinge wrote:
>   
>> Chuck Ebbert wrote:
>>     
>>> What CPU architecture is this happening on? Not i686 with PAE by
>>> any chance?
>>>       
>> Yes.  Why?
>>     
>
> I have a bug report where NFS files are corrupted only with PAE clients.
> Corruption is at the end of the (newly untarred) files. Doesn't happen
> without PAE.
>   

Hm, suggestive, but I'm not convinced.  Two differences to this situation:

   1. Immediately after the clone ("untar"), the contents are completely
      OK; it's only after a umount/mount cycle to problems appear
   2. There's no corruption as such; the files are just too short.  And
      it seems they're at a previously OK length, not some random size.

    J
-
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/