[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1171989496.6271.32.camel@heimdal.trondhjem.org>
Date: Tue, 20 Feb 2007 11:38:16 -0500
From: Trond Myklebust <trond.myklebust@....uio.no>
To: Chris Mason <chris.mason@...cle.com>
Cc: Benjamin LaHaise <bcrl@...ck.org>,
"Ananiev, Leonid I" <leonid.i.ananiev@...el.com>,
Zach Brown <zach.brown@...cle.com>, linux-aio@...ck.org,
linux-kernel@...r.kernel.org,
Suparna bhattacharya <suparna@...ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] aio: propogate post-EIOCBQUEUED errors to completion
event
On Tue, 2007-02-20 at 11:30 -0500, Trond Myklebust wrote:
> > One option is to have invalidate_inode_pages2_range continue if it can't
> > toss a page but still return something that O_DIRECT ignores (living
> > with the race), but it looks like I can make a launder_page op that does
> > the right thing. I'll give it a shot.
>
> I already sent in a patch to do that last week.
To be more precise, here are the 2 patches that I sent to lkml last
week. One ensures that we don't stop the invalidation just because of
the existence of an unsynced dirty page. The other gets rid of the EIO
for that case.
Cheers
Trond
Download attachment "linux-2.6.20-001-fix_invalidate_inode_pages2_range_return.dif" of type "message/rfc822" (1156 bytes)
Download attachment "linux-2.6.20-002-invalidate_inode_pages2_dont_fail_on_dirty.dif" of type "message/rfc822" (1857 bytes)
Powered by blists - more mailing lists