From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: serue@us.ibm.com, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: TOMOYO Linux Security Goal
Date: Mon, 31 Dec 2007 10:17:21 -0600 [thread overview]
Message-ID: <20071231161721.GA29992@sergelap.austin.ibm.com> (raw)
In-Reply-To: <200801010025.DDC48911.SOLOMQFFHVFtOJ@I-love.SAKURA.ne.jp>
Quoting Tetsuo Handa (penguin-kernel@I-love.SAKURA.ne.jp):
> Hello.
>
> Serge E. Hallyn wrote:
> > > Does a process get different mount trees by just calling clone() or unshare()?
> > > My understanding is that clone() or unshare() disables propergation of
> > > mount tree changes when somebody calls mount() or umount() or pivot_root().
> >
> > Yes, with further propagation rules possible.
> >
> Excuse me. To which statement did you say "yes"?
Sorry, "yes your understanding was correct."
> Does clone() or unshare() change visible directories without
> calling following mount()/umount()/pivot_root()?
>
> Regards.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-12-31 16:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-25 12:33 Tetsuo Handa
2007-12-26 16:42 ` Serge E. Hallyn
2007-12-27 13:00 ` Tetsuo Handa
2007-12-27 14:54 ` Serge E. Hallyn
2007-12-28 14:32 ` Tetsuo Handa
2007-12-28 15:12 ` Serge E. Hallyn
2007-12-29 3:43 ` Tetsuo Handa
2007-12-31 15:17 ` Serge E. Hallyn
2007-12-31 15:25 ` Tetsuo Handa
2007-12-31 16:17 ` Serge E. Hallyn [this message]
2007-12-28 17:23 ` Valdis.Kletnieks
2007-12-30 0:02 ` Pavel Machek
2007-12-30 5:29 ` Tetsuo Handa
2007-12-30 6:28 ` Valdis.Kletnieks
2007-12-31 15:27 ` Casey Schaufler
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=20071231161721.GA29992@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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®