mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@digeo.com>
Subject: Re: [PATCH COW] remove struct file from readpage() and friends
Date: Mon, 19 Apr 2004 14:19:18 +0200	[thread overview]
Message-ID: <20040419121917.GA15276@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <m1llkuqbzh.fsf@ebiederm.dsl.xmission.com>

On Sat, 17 April 2004 20:02:58 -0600, Eric W. Biederman wrote:
> Jörn Engel <joern@wohnheim.fh-wedel.de> writes:
> 
> > this could be a good idea, it could also be utterly insane.  If anyone
> > knows for sure, please tell me.
> > 
> > The point is that copyfile(), one of the ingredients to cowlinks,
> > currently has to open() the source, because sendfile() requires a
> > struct file* as one of the arguments.  Following the path down shows
> > that this struct file* is almost never used, but ultimately required
> > by readpage() and readpages().
> > 
> > Those two, again, almost never use the struct file*, except for five
> > cases.  One was trivial to fix, nfs, smbfs, cifs and blkmtd remain:
> 
> Interface wise there are per user credentials that need to remain with
> the written data.  These credentials by there very nature are per
> file.

Not really.  For nfs3, they appear to be per *user*, just accessed in
a funny way.  nfs4 looks a little more complicated, but in the end,
all data is either accessable by other means or used for locking.
Does locking work on NFS now?  If not, that can go as well.

Looks like I will keep this patch for a while and see what Linus
thinks when 2.7 opens up.

Jörn

-- 
The cheapest, fastest and most reliable components of a computer
system are those that aren't there.
-- Gordon Bell, DEC labratories

      reply	other threads:[~2004-04-19 12:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-16 12:26 Jörn Engel
2004-04-18  2:02 ` Eric W. Biederman
2004-04-19 12:19   ` Jörn Engel [this message]

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=20040419121917.GA15276@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=akpm@digeo.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®