From: Lukasz Pawelczyk <l.pawelczyk@samsung.com>
To: Richard Weinberger <richard@nod.at>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
James Morris <james.l.morris@oracle.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
Serge Hallyn <serge.hallyn@canonical.com>,
Al Viro <viro@zeniv.linux.org.uk>, Paul Moore <pmoore@redhat.com>,
Kees Cook <keescook@chromium.org>,
Miklos Szeredi <mszeredi@suse.cz>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Nikolay Aleksandrov <nikolay@redhat.com>,
Mark Rustad <mark.d.rustad@intel.com>,
David Howells <dhowells@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>,
Juri Lelli <juri.lelli@gmail.com>,
Daeseok Youn <daeseok.youn@gmail.com>,
David Rientjes <rientjes@google.com>,
Dario Faggioli <raistlin@linux.it>,
Alex Thorlton <athorlton@sgi.com>,
Matthew Dempsky <mdempsky@chromium.org>,
Vladimir Davydov <vdavydov@parallels.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Casey Schaufler <casey@schaufler-ca.com>,
LKML <linux-kernel@vger.kernel.org>,
"open list:ABI/API" <linux-api@vger.kernel.org>,
linux-security-module@vger.kernel.org,
Linux Containers <containers@lists.linux-foundation.org>,
Lukasz Pawelczyk <havner@gmail.com>
Subject: Re: [RFC] lsm: namespace hooks
Date: Thu, 27 Nov 2014 16:24:22 +0100 [thread overview]
Message-ID: <1417101862.1805.23.camel@samsung.com> (raw)
In-Reply-To: <547740A0.4040700@nod.at>
On czw, 2014-11-27 at 16:17 +0100, Richard Weinberger wrote:
> Am 27.11.2014 um 16:11 schrieb Lukasz Pawelczyk:
> > On czw, 2014-11-27 at 16:01 +0100, Richard Weinberger wrote:
> >> Am 27.11.2014 um 15:44 schrieb Lukasz Pawelczyk:
> >>> True, the last one is 0x80000000. I did not notice that. Thanks for
> >>> pointing out.
> >>
> >> Isn't this CLONE_IO?
> >
> > Yes, I was merely noticing out loud that it's the last bit of 32bit.
> >
> > After close look though the 0x00001000 appears to be unused
>
> This was CLONE_PID.
> I'm not sure if we can reuse this. man 2 clone states "It disappeared in Linux 2.5.16.".
> Maybe one of the CC'd parties can tell more...
Would really like someone to comment on this. I'd like to avoid creating
a new syscall at this point.
According to clone(2):
CLONE_STOPPED has been removed in 2.6.38 and can be reused.
CLONE_PID as you mentioned has been removed in 2.5.16 but since 2.3.21
it could only be used by boot process (PID 0).
So this was really long time ago and effectively regular user space
cannot use it since 2.3.21.
--
Lukasz Pawelczyk
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2014-11-27 15:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 14:01 [RFC] LSM/Smack namespace work in progress Lukasz Pawelczyk
2014-11-27 14:01 ` [RFC] lsm: namespace hooks Lukasz Pawelczyk
2014-11-27 14:18 ` Richard Weinberger
2014-11-27 14:35 ` Lukasz Pawelczyk
[not found] ` <54773757.8090905@nod.at>
2014-11-27 14:44 ` Lukasz Pawelczyk
[not found] ` <54773CE7.5040303@nod.at>
2014-11-27 15:11 ` Lukasz Pawelczyk
[not found] ` <547740A0.4040700@nod.at>
2014-11-27 15:24 ` Lukasz Pawelczyk [this message]
2014-11-27 15:42 ` Eric W. Biederman
2014-11-27 16:07 ` Lukasz Pawelczyk
2014-11-27 16:44 ` Eric W. Biederman
2014-11-27 17:38 ` Lukasz Pawelczyk
2014-12-02 12:43 ` Lukasz Pawelczyk
2014-12-09 16:13 ` 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=1417101862.1805.23.camel@samsung.com \
--to=l.pawelczyk@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=athorlton@sgi.com \
--cc=casey@schaufler-ca.com \
--cc=containers@lists.linux-foundation.org \
--cc=daeseok.youn@gmail.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=havner@gmail.com \
--cc=james.l.morris@oracle.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=juri.lelli@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mark.d.rustad@intel.com \
--cc=mdempsky@chromium.org \
--cc=mingo@redhat.com \
--cc=mszeredi@suse.cz \
--cc=nikolay@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=pmoore@redhat.com \
--cc=raistlin@linux.it \
--cc=richard@nod.at \
--cc=rientjes@google.com \
--cc=serge.hallyn@canonical.com \
--cc=serge@hallyn.com \
--cc=vdavydov@parallels.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