From: Miklos Szeredi <miklos-sUDqSbJrdHQHWmgEVkV9KA@public.gmane.org>
To: Seth Forshee <seth.forshee-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Cc: fuse-devel
<fuse-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Serge Hallyn
<serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>,
Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Andy Lutomirski <luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org>,
"Eric W. Biederman"
<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>,
Linux-Fsdevel
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: fuse_get_context() and namespaces
Date: Mon, 1 Jun 2015 15:07:07 +0200 [thread overview]
Message-ID: <CAJfpegv1AOHjLUtfUHDD8BWiQBs4Ug83RsthPuF206mqYePXFg@mail.gmail.com> (raw)
In-Reply-To: <20150527125546.GA22018@ubuntu-xps13>
On Wed, May 27, 2015 at 2:55 PM, Seth Forshee
<seth.forshee-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org> wrote:
> I haven't seen anything to indicate that this filesystem will be broken
> by this, just that it's broken by untranslated pids. Presumably it would
> just reject any requests which aren't representable in its namespace.
Without failing the operation there never will be any indication that
a filesystem is broken. So I guess the safe way would be
- deny access for untranslated pids (uids, gids, etc).
- if this becomes an issue (possibly a perfomance issue), then add a
flag to disable pids (and/or uids, gids) completely.
Thanks,
Miklos
------------------------------------------------------------------------------
next prev parent reply other threads:[~2015-06-01 13:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150331011423.GC13083@unsen.q53.spb.ru>
[not found] ` <20150401155515.GA2994@unsen.q53.spb.ru>
[not found] ` <CAJfpegvYrJBmnfqk0zO6EWbaiqxuN4anx6Fpw07_P5+s0P1RVw@mail.gmail.com>
[not found] ` <20150502155623.GD13083@unsen.q53.spb.ru>
2015-05-22 14:23 ` [fuse-devel] fuse_get_context() and namespaces Miklos Szeredi
2015-05-22 14:47 ` Seth Forshee
2015-05-22 17:44 ` Eric W. Biederman
2015-05-22 18:59 ` Seth Forshee
2015-05-26 15:21 ` Miklos Szeredi
2015-05-26 16:14 ` [fuse-devel] " Seth Forshee
2015-05-27 3:31 ` Eric W. Biederman
2015-05-27 12:55 ` Seth Forshee
2015-06-01 13:07 ` Miklos Szeredi [this message]
2015-06-03 14:03 ` Seth Forshee
2015-05-22 17:32 ` Eric W. Biederman
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=CAJfpegv1AOHjLUtfUHDD8BWiQBs4Ug83RsthPuF206mqYePXFg@mail.gmail.com \
--to=miklos-sudqsbjrdhqhwmgevkv9ka@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=fuse-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org \
--cc=serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org \
--cc=seth.forshee-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.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;
as well as URLs for NNTP newsgroup(s).