From: Mike Galbraith <gleep@gmx.de>
To: Jan Kara <jack@suse.cz>
Cc: James Y Knight <foom@fuhm.net>,
LKML <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org, npiggin@suse.de
Subject: Re: writev data loss bug in (at least) 2.6.31 and 2.6.32pre8 x86-64
Date: Tue, 01 Dec 2009 17:47:58 +0100 [thread overview]
Message-ID: <1259686078.6229.1.camel@marge.simson.net> (raw)
In-Reply-To: <20091201160324.GA25873@quack.suse.cz>
On Tue, 2009-12-01 at 17:03 +0100, Jan Kara wrote:
> The patch below fixes the issue for me...
Ditto.
-Mike
next prev parent reply other threads:[~2009-12-01 16:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1F5364AE-321E-44E9-8B0D-B8E17597A0DA@fuhm.net>
[not found] ` <907888CC-F4B2-448F-8F48-B96A566D323B@fuhm.net>
[not found] ` <1259667765.9614.19.camel@marge.simson.net>
2009-12-01 14:35 ` writev data loss bug in (at least) 2.6.31 and 2.6.32pre8 x86-64 Jan Kara
2009-12-01 16:03 ` Jan Kara
2009-12-01 16:47 ` Mike Galbraith [this message]
2009-12-01 22:02 ` Andreas Dilger
2009-12-02 18:53 ` Randy Dunlap
2009-12-03 15:11 ` [LTP] " Subrata Modak
2009-12-02 21:24 ` James Y Knight
2009-12-02 19:04 ` Jan Kara
2009-12-03 5:28 ` Nick Piggin
2009-12-03 10:32 ` Jan Kara
2009-12-03 5:22 ` Nick Piggin
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=1259686078.6229.1.camel@marge.simson.net \
--to=gleep@gmx.de \
--cc=foom@fuhm.net \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).