Re: writev data loss bug in (at least) 2.6.31 and 2.6.32pre8 x86-64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Jan Kara <jack@xxxxxxx>
Subject: Re: writev data loss bug in (at least) 2.6.31 and 2.6.32pre8 x86-64
From: Mike Galbraith <gleep@xxxxxx>
Date: Tue, 01 Dec 2009 17:47:58 +0100
Cc: James Y Knight <foom@xxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, linux-ext4@xxxxxxxxxxxxxxx, npiggin@xxxxxxx
In-reply-to: <20091201160324.GA25873@xxxxxxxxxxxxx>

On Tue, 2009-12-01 at 17:03 +0100, Jan Kara wrote:

>   The patch below fixes the issue for me...

Ditto.

	-Mike

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

References:
- Re: writev data loss bug in (at least) 2.6.31 and 2.6.32pre8 x86-64
  - From: Jan Kara
- Re: writev data loss bug in (at least) 2.6.31 and 2.6.32pre8 x86-64
  - From: Jan Kara

Prev by Date: Re: writev data loss bug in (at least) 2.6.31 and 2.6.32pre8 x86-64
Next by Date: [PATCH] ext4: Remove blocks from inode prealloc list on failure
Previous by thread: Re: writev data loss bug in (at least) 2.6.31 and 2.6.32pre8 x86-64
Next by thread: Re: writev data loss bug in (at least) 2.6.31 and 2.6.32pre8 x86-64
Index(es):
- Date
- Thread

[Index of Archives] [Reiser Filesystem Development] [Ceph FS] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Linux FS] [Yosemite National Park] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Device Mapper] [Linux Media]

Powered by Linux