From: Seth Forshee <seth.forshee@canonical.com>
To: Miklos Szeredi <miklos@szeredi.hu>,
Alexander Viro <viro@zeniv.linux.org.uk>,
"Eric W. Biederman" <ebiederm@xmission.com>
Cc: Serge Hallyn <serge.hallyn@ubuntu.com>,
fuse-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] fuse: Add support for mounts from pid/user namespaces
Date: Tue, 23 Sep 2014 09:28:07 -0500 [thread overview]
Message-ID: <20140923142807.GB19016@ubuntu-hedt> (raw)
In-Reply-To: <1410532905-114262-1-git-send-email-seth.forshee@canonical.com>
On Fri, Sep 12, 2014 at 09:41:41AM -0500, Seth Forshee wrote:
> Third round of patches for making it possible to mount with fuse from
> within user namespaces. The only change since v2 is the addition of a
> patch to ensure real root is capable towards inodes whose uid/gid is
> invalid.
It's been nearly two weeks (three from the v2 patches) without any
feedback besides Serge's acks. Any other comments or objections? Anyone
planning to pick these up?
Thanks,
Seth
next prev parent reply other threads:[~2014-09-23 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 14:41 [PATCH v3 0/4] fuse: Add support for mounts from pid/user namespaces Seth Forshee
[not found] ` <1410532905-114262-1-git-send-email-seth.forshee-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2014-09-12 14:41 ` [PATCH v3 1/4] vfs: Check for invalid i_uid in may_follow_link() Seth Forshee
2014-09-12 14:41 ` [PATCH v3 2/4] vfs, userns: Ensure real root is always capable towards inodes Seth Forshee
2014-09-12 17:13 ` [PATCH v3 2/4] vfs,userns: " Serge Hallyn
2014-09-12 14:41 ` [PATCH v3 3/4] fuse: Translate pids passed to userspace into pid namespaces Seth Forshee
2014-09-12 14:41 ` [PATCH v3 4/4] fuse: Add support for mounts from user namespaces Seth Forshee
2014-09-23 14:28 ` Seth Forshee [this message]
2014-09-23 17:08 ` [PATCH v3 0/4] fuse: Add support for mounts from pid/user namespaces Serge E. Hallyn
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=20140923142807.GB19016@ubuntu-hedt \
--to=seth.forshee@canonical.com \
--cc=ebiederm@xmission.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=serge.hallyn@ubuntu.com \
--cc=viro@zeniv.linux.org.uk \
/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).