[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4D4A9533.4090304@panasas.com>
Date: Thu, 03 Feb 2011 13:44:51 +0200
From: Boaz Harrosh <bharrosh@...asas.com>
To: Nick Piggin <npiggin@...nel.dk>
CC: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-ext4@...r.kernel.org, Roman Zippel <zippel@...ux-m68k.org>,
"Tigran A. Aivazian" <tigran@...azian.fsnet.co.uk>,
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>,
Dave Kleikamp <shaggy@...ux.vnet.ibm.com>,
Bob Copeland <me@...copeland.com>,
reiserfs-devel@...r.kernel.org,
Christoph Hellwig <hch@...radead.org>,
Evgeniy Dushistov <dushistov@...l.ru>, Jan Kara <jack@...e.cz>
Subject: Re: [PATCH] exofs: simple fsync race fix
On 11/25/2010 01:50 PM, Nick Piggin wrote:
> This is fine, we'll get it merged before 2.6.37, just give a couple of
> days for review, I haven't had much confirmation from other vfs people
> about these problems.
>
> Thanks,
> Nick
>
Hi Dear Nick.
So I was cleaning the table and I fell on this patch. What ever happened
to it? should I push it through my tree?
Thanks
Boaz
> On Thu, Nov 25, 2010 at 12:52:08PM +0200, Boaz Harrosh wrote:
>> From: Nick Piggin <npiggin@...nel.dk>
>>
>> It is incorrect to test inode dirty bits without participating in the inode
>> writeback protocol. Inode writeback sets I_SYNC and clears I_DIRTY_?, then
>> writes out the particular bits, then clears I_SYNC when it is done. BTW. it
>> may not completely write all pages out, so I_DIRTY_PAGES would get set
>> again.
>>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists