lkml.org 
[lkml]   [2006]   [Mar]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Introduce sys_splice() system call
On Thu, Mar 30 2006, Andrew Morton wrote:
> Jens Axboe <axboe@suse.de> wrote:
> >
> > > > + ret = write_one_page(page, 0);
> > >
> > > Still want to know why this is here??
> > >
> > > > +out:
> > > > + if (ret < 0)
> > > > + unlock_page(page);
> > >
> > > If write_one_page()'s call to ->writepage() failed, this will cause a
> > > double unlock.
> >
> > Can probably be improved - can I drop write_one_page() and just unlock
> > the page and regular cleaning will flush it out?
> >
>
> Of course - commit_write() will mark the page dirty and it'll get flushed
> back in the normal manner. We don't need that set_page_dirty() in there
> either.

Ok, wasn't sure about the fact if it always dirtied the page for me.
I'll test it and get rid of it.

> But we do need some O_SYNC/S_ISSYNC handling...

Hrmpf so that isn't handled automagically. Noted.

--
Jens Axboe

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-03-31 09:35    [W:0.064 / U:0.096 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site