From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: "Latchesar Ionkov" <lucho@ionkov.net>
Cc: linux-kernel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] 9p: attach-per-user
Date: Thu, 13 Sep 2007 09:20:23 -0500 [thread overview]
Message-ID: <a4e6962a0709130720o457a3f7ene7977d99720b2d30@mail.gmail.com> (raw)
In-Reply-To: <20070913044803.GC2675@ionkov.net>
On 9/12/07, Latchesar Ionkov <lucho@ionkov.net> wrote:
>
> - allow only one user to access the tree (access=<uid>)
> Only the user with uid can access the v9fs tree. Other users that attempt
> to access it will get EPERM error.
>
While access=<uid> and dfltuid=<some-other-uid> creates an interesting
flexibility in the way things can be used, I'm wondering if
access=<uid> dfltuid=DEFAULT_UID is intuitive, it might be nice for
the default behavior to be setting defltuid to the uid specified in
access when that access option is used. This can be overridden with
the dfltuid option, but I think it makes more sense to attach as the
uid you are restricting access to.
If that's the way we want to go, I think that can be handled in a
separate patch.
I've merged this stuff into my test tree, as soon as regressions pass
and I confirm they compile clean on another architecture I'll push
them into my devel to be picked up by -mm.
-eric
next prev parent reply other threads:[~2007-09-13 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 4:48 [PATCH] 9p: attach-per-user Latchesar Ionkov
2007-09-13 14:20 ` Eric Van Hensbergen [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-03 20:18 Latchesar Ionkov
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=a4e6962a0709130720o457a3f7ene7977d99720b2d30@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=v9fs-developer@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).