[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080731001131.GA30900@shareable.org>
Date: Thu, 31 Jul 2008 01:11:31 +0100
From: Jamie Lokier <jamie@...reable.org>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: torvalds@...ux-foundation.org, jens.axboe@...cle.com,
akpm@...ux-foundation.org, nickpiggin@...oo.com.au,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [patch v3] splice: fix race with page invalidation
> > And by papering it over, it then just makes people less likely to bother
> > with the real issue.
>
> I think you are talking about a totally separate issue: that NFSD's
> use of splice can result in strange things if the file is truncated
> while being read. But this is an NFSD issue and I don't see that it
> has _anything_ to do with the above bug in splice. I think you are
> just confusing the two things.
I'm more concerned by sendfile() users like Apache, Samba, FTPd. In
an earlier thread on this topic, I asked if the splice bug can also
result in sendfile() sending blocks of zeros, when a file is truncated
after it has been sent, and the answer was yes probably.
Not that I checked or anything. But if it affects sendfile() it's a
bigger deal - that has many users.
Assuming it does affect sendfile(), it's exasperated by not being able
to tell when a sendfile() has finished with the pages its sending.
E.g. you can't lock the file or otherwise synchronise with another
program which wants to modify the file.
-- Jamie
--
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