From: Matthew Wilcox <matthew@wil.cx>
To: "Igor A. Nesterov" <igor.nesterov@indexengines.com>
Cc: James.Smart@Emulex.Com, Tore Anderson <tore@linpro.no>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org
Subject: Re: Linux 2.6.23-rc3
Date: Wed, 15 Aug 2007 08:47:23 -0600 [thread overview]
Message-ID: <20070815144723.GZ16277@parisc-linux.org> (raw)
In-Reply-To: <1187186897.1457.57.camel@potomac.tworiverlabs.com>
On Wed, Aug 15, 2007 at 10:08:17AM -0400, Igor A. Nesterov wrote:
> So would it be true to say that the fix for -EEXIST problem still has
> not found its way to mainline kernel? I've been hit by this problem
> after switching to Fedora 7, and currently running on Fedora
> 2.6.21-1.3228 kernel patched with one of those fixes above. I always
> hoped that 2.6.22 will be free of this problem, but apparently it still
> exists even in 2.6.23.
James Bottomley just added it to the tree that will be pushed for the
2.6.24 merge window. I'd wish for it to be added to 2.6.23 too, since
it does fix a bug, but it's his decision, not mine.
--
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2007-08-15 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.0.999.0708122143240.30176@woody.linux-foundation.org>
2007-08-14 9:10 ` Linux 2.6.23-rc3 Tore Anderson
2007-08-14 11:24 ` Matthew Wilcox
2007-08-14 13:04 ` James Smart
[not found] ` <1187186897.1457.57.camel@potomac.tworiverlabs.com>
2007-08-15 14:47 ` Matthew Wilcox [this message]
2007-08-14 18:31 ` Tore Anderson
2007-08-15 12:59 ` Tore Anderson
2007-08-14 12:25 ` James Smart
2007-08-14 13:07 ` Tore Anderson
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=20070815144723.GZ16277@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Smart@Emulex.Com \
--cc=igor.nesterov@indexengines.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tore@linpro.no \
--cc=torvalds@linux-foundation.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox