LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mark Lord <lkml@rtr.ca>, Bron Gondwana <brong@fastmail.fm>,
Mike Houston <mikeserv@bmts.com>,
Chuck Ebbert <cebbert@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Steve French <smfltc@us.ibm.com>,
Dave Kleikamp <shaggy@linux.vnet.ibm.com>,
Daniel Drake <dsd@gentoo.org>,
samba-technical@lists.samba.org,
Vladimir Saveliev <vs@namesys.com>,
reiserfs-dev@namesys.com, David Chinner <dgc@sgi.com>,
xfs-masters@oss.sgi.com
Subject: Re: How many people are using 2.6.16?
Date: Wed, 31 Jan 2007 08:02:37 +0100 [thread overview]
Message-ID: <20070131070237.GT3754@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0701301748230.3611@woody.linux-foundation.org>
On Tue, Jan 30, 2007 at 06:36:48PM -0800, Linus Torvalds wrote:
>
>
> On Tue, 30 Jan 2007, Mark Lord wrote:
> >
> > I believe our featherless leader said he though it was an ancient bug,
> > exasperated by something that went into 2.6.19.
> >
> > If Linus's opinion is correct (still?), then the bug exists in all
> > kernels since somewhere back in the 2.4.xx days.
>
> The issue was somewhat confused by people certainly *reporting* it for
> older kernels. Also, as part of the dirty bit cleanups and sanity
> checkingwe did actually seem to fix a long-standing CIFS corruption (and
> apparently reisertfs/XFS problems too).
>
> But the *common* case was actually introduced with 2.6.19, and 2.6.16
> wouldn't be affected.
Thanks for the clarifications.
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
> Linus
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-01-31 7:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 20:30 Chuck Ebbert
2007-01-29 20:35 ` Josh Boyer
2007-01-29 20:38 ` Chuck Ebbert
2007-02-07 20:36 ` Greg KH
2007-01-29 21:04 ` Mike Houston
2007-01-29 22:13 ` Bron Gondwana
2007-01-30 20:39 ` Adrian Bunk
2007-01-31 1:33 ` Mark Lord
2007-01-31 2:36 ` Linus Torvalds
2007-01-31 5:49 ` Bron Gondwana
2007-01-31 7:02 ` Adrian Bunk [this message]
2007-01-31 10:42 ` Reiserfs and MMAP (was: How many people are using 2.6.16?) Bron Gondwana
2007-01-31 11:49 ` How many people are using 2.6.16? David Chinner
2007-01-31 14:34 ` Steve French (smfltc)
2007-01-31 15:34 ` Linus Torvalds
2007-02-01 12:13 ` Vladimir V. Saveliev
2007-02-03 1:39 ` Adrian Bunk
2007-01-30 23:52 ` Adrian Bunk
2007-01-31 1:48 ` Mike Houston
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070131070237.GT3754@stusta.de \
--to=bunk@stusta.de \
--cc=brong@fastmail.fm \
--cc=cebbert@redhat.com \
--cc=dgc@sgi.com \
--cc=dsd@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=mikeserv@bmts.com \
--cc=reiserfs-dev@namesys.com \
--cc=samba-technical@lists.samba.org \
--cc=shaggy@linux.vnet.ibm.com \
--cc=smfltc@us.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=vs@namesys.com \
--cc=xfs-masters@oss.sgi.com \
--subject='Re: How many people are using 2.6.16?' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).