| To: | Lachlan McIlroy <lachlan@xxxxxxx> |
|---|---|
| Subject: | Re: [Fwd: [PATCH] Fix race in xfs_write() between direct and buffered I/O with DMAPI] |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Tue, 23 Dec 2008 03:40:13 -0500 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx> |
| In-reply-to: | <49503378.2080508@sgi.com> |
| References: | <493779B1.3010703@sgi.com> <20081208225125.GA15647@infradead.org> <493DFDBD.7060909@sgi.com> <20081209092240.GA23915@infradead.org> <20081222085311.GB24795@infradead.org> <49503378.2080508@sgi.com> |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
On Tue, Dec 23, 2008 at 11:40:24AM +1100, Lachlan McIlroy wrote: > Christoph Hellwig wrote: > > Do you need more input on this one? > > Actually I just might. Based on your last reponse I wasn't sure if > you wanted me to make further changes. Well, my reponse was that I think we could do it more effecient, but the patch still looks correct to me. > Then I got side-tracked wondering > why we even have the 'goto retry' in the dmapi post event - why retry the > write if we get ENOSPC when we don't if dmapi is not enabled? Could the > write get stuck in an infinite loop? We only retry on ENOSPC if the dmapi nospace even is enabled, or am I missing something? |
| Previous by Date: | [XFS updates] XFS development tree branch, master, updated. v2.6.28-rc3-1828-gad1ad96, xfs |
|---|---|
| Next by Date: | Yo! Media: Justin Timberlake ft. T.I. - If I [+ MORE], Yo! Raps |
| Previous by Thread: | Re: [Fwd: [PATCH] Fix race in xfs_write() between direct and buffered I/O with DMAPI], Lachlan McIlroy |
| Next by Thread: | Re: [Fwd: [PATCH] Fix race in xfs_write() between direct and buffered I/O with DMAPI], Lachlan McIlroy |
| Indexes: | [Date] [Thread] [Top] [All Lists] |