From: ebiederm@xmission.com (Eric W. Biederman)
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@digeo.com>
Subject: Re: [PATCH COW] remove struct file from readpage() and friends
Date: 17 Apr 2004 20:02:58 -0600 [thread overview]
Message-ID: <m1llkuqbzh.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20040416122652.GA24859@wohnheim.fh-wedel.de>
Jörn Engel <joern@wohnheim.fh-wedel.de> writes:
> Folks,
>
> 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.
Last I heard the current interface was only a rough approximation of
correct in that it is wrong if you are caching data and you have
multiple people writing per file.
So definitely at the top level you should have a struct file
so that the credentials needed can be computed. As things
filter down it may be possible to change that.
Eric
next prev parent reply other threads:[~2004-04-18 2:03 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 [this message]
2004-04-19 12:19 ` Jörn Engel
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=m1llkuqbzh.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@digeo.com \
--cc=joern@wohnheim.fh-wedel.de \
--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®