public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Petr Vandrovec <VANDROVE@vc.cvut.cz>,
	linux-kernel@vger.kernel.org, richard@bouska.cz
Subject: Re: NFS mountned  directory  and apache2 (2.5.47)
Date: Sat, 16 Nov 2002 04:44:54 +0000	[thread overview]
Message-ID: <20021116044454.A31763@infradead.org> (raw)
In-Reply-To: <15829.24239.643774.231548@helicity.uio.no>; from trond.myklebust@fys.uio.no on Fri, Nov 15, 2002 at 09:53:03PM +0100

On Fri, Nov 15, 2002 at 09:53:03PM +0100, Trond Myklebust wrote:
>      > Linus removed that in early 2.5 because it led to kmap()
>      > deadlocks.  sendfile can fail with EINVAL and userspace must
>      > not rely on it working on any object.
> 
> Fair enough. The kernel may not be the appropriate place for providing
> such an emulation, but there's no reason why glibc shouldn't be able
> to do so for the case where sendfile returns EINVAL.

*nod*

> However none of this changes the matter of the NFS client. The latter
> *does* support a pagecache, and so the one-line patch is appropriate.

just a little bit more then one line :)  nfs needs to do the same
revalidation as in nfs_file_read and then call generic_file_sendfile.


  reply	other threads:[~2002-11-16  4:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-15 18:19 NFS mountned directory and apache2 (2.5.47) Petr Vandrovec
2002-11-15 20:16 ` Trond Myklebust
2002-11-15 20:26   ` Christoph Hellwig
2002-11-15 20:53     ` Trond Myklebust
2002-11-16  4:44       ` Christoph Hellwig [this message]
2002-11-17 20:18         ` Trond Myklebust
2002-11-15 21:10     ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2002-11-15 10:25 Richard Bouska
2002-11-15 18:10 ` Trond Myklebust

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021116044454.A31763@infradead.org \
    --to=hch@infradead.org \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard@bouska.cz \
    --cc=trond.myklebust@fys.uio.no \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox