linux-kernel - Re: XFS error & call trace

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20090123055109.GA25601@x61>
Date:	Fri, 23 Jan 2009 06:51:09 +0100
From:	Tino Keitel <tino.keitel@....de>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Lars Noschinski <lkml@...noschinski.de>,
	linux-kernel@...r.kernel.org
Subject: Re: XFS error & call trace

On Wed, Jan 21, 2009 at 18:14:35 -0500, Christoph Hellwig wrote:
> On Wed, Jan 21, 2009 at 11:27:03PM +0100, Lars Noschinski wrote:
> > Hello!
> > 
> > I just had a crash of my XFS file system on 2.6.29-rc1 (syslog output
> > follows) After this, the file system on /home returned -EIO on most (all?)
> > operations.  After a reboot from cdrom, I found it interesting to see that
> > xfs_check found no error on this partition. Instead, the XFS on the /
> > partition had a lot of errors.
> 
> The patch below from Dave Chinner fixes it:
> 
> ---
> 
> [XFS] Long btree pointers are still 64 bit on disk
> 
> On 32 bit machines with CONFIG_LBD=n, XFS reduces the
> in memory size of xfs_fsblock_t to 32 bits so that it
> will fit within 32 bit addressing. However, the disk format
> for long btree pointers are still 64 bits in size.
> 
> The recent btree rewrite failed to take this into account

Hi,

does this commit also fix http://lkml.org/lkml/2009/1/7/324 ?

Regards,
Tino
--
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/