xfs-masters
[Top] [All Lists]

[xfs-masters] Re: How many people are using 2.6.16?

To: Adrian Bunk <bunk@xxxxxxxxx>
Subject: [xfs-masters] Re: How many people are using 2.6.16?
From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Date: Wed, 31 Jan 2007 07:34:35 -0800 (PST)
Cc: Mark Lord <lkml@xxxxxx>, Bron Gondwana <brong@xxxxxxxxxxx>, Mike Houston <mikeserv@xxxxxxxx>, Chuck Ebbert <cebbert@xxxxxxxxxx>, linux-kernel <linux-kernel@xxxxxxxxxxxxxxx>, Steve French <smfltc@xxxxxxxxxx>, Dave Kleikamp <shaggy@xxxxxxxxxxxxxxxxxx>, Daniel Drake <dsd@xxxxxxxxxx>, samba-technical@xxxxxxxxxxxxxxx, Vladimir Saveliev <vs@xxxxxxxxxxx>, reiserfs-dev@xxxxxxxxxxx, David Chinner <dgc@xxxxxxx>, xfs-masters@xxxxxxxxxxx
In-reply-to: <20070131070237.GT3754@xxxxxxxxx>
References: <45BE5948.6060403@xxxxxxxxxx> <20070129160448.65fc63f3.mikeserv@xxxxxxxx> <20070129221300.GC19422@xxxxxxxxx> <20070130203933.GJ3754@xxxxxxxxx> <45BFF1F4.3060401@xxxxxx> <Pine.LNX.4.64.0701301748230.3611@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20070131070237.GT3754@xxxxxxxxx>
Reply-to: xfs-masters@xxxxxxxxxxx
Sender: xfs-masters-bounce@xxxxxxxxxxx

On Wed, 31 Jan 2007, Adrian Bunk wrote:
> 
> Regarding the longstanding CIFS/reiserfs/XFS problems, it seems the 
> status is:
> 
> CIFS:
> commit cb876f451455b6187a7d69de2c112c45ec4b7f99
>   Fix up CIFS for "test_clear_page_dirty()" removal
> queued for 2.6.19.3
> applies and compiles against 2.6.16
> 
> reiserfs:
> commit de14569f94513279e3d44d9571a421e9da1759ae
>   [PATCH] resierfs: avoid tail packing if an inode was ever mmapped
> backport to 2.6.16 required
> 
> XFS:
> fix not yet in your tree

Yes. The XFS problem should only be triggerable through O_DIRECT and 
non-O_DIRECT mmap at the same time, so the fix for that got pushed back as 
noncritical.

NOTE! I'm still not 100% sure about the older bdb corruption reports. Were 
they just noise due to other issues? Flaky RAM? One report of corruption 
was actually due to running my test-program without enough diskspace, so 
while that confused the issue for a while, it turned out to be a 
non-issue.

So I'm just saying that there might be other things lurking too. 

                Linus


<Prev in Thread] Current Thread [Next in Thread>