From: Oleg Nesterov <oleg@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: peterz@infradead.org, linux-kernel@vger.kernel.org,
linux-audit@redhat.com, stable@vger.kernel.org,
akpm@linux-foundation.org,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH 7/7] pid: get pid_t ppid of task in init_pid_ns
Date: Mon, 24 Feb 2014 19:32:32 +0100 [thread overview]
Message-ID: <20140224183232.GA21474@redhat.com> (raw)
In-Reply-To: <20140221181055.GE17952@madcap2.tricolour.ca>
On 02/21, Richard Guy Briggs wrote:
>
> On 14/02/20, Oleg Nesterov wrote:
> >
> > imho it would be better to send this patch along with sys_getppid()
> > conversions, but I won't argue.
>
> I don't think sys_getppid() should be changed since it is a syscall
> whose userspace user would assume the working namespace.
Sorry for confusion, I didn't mean we need to change sys_getppid(),
> Many of the
> kernel internal uses of it are likely wrong though, so fixing that
> should probably fall under another patch. I fixed audit in another
> patch.
Yes, this is what I meant. And this patch should probably go into
that series which fixes the in-kernel users of sys_getppid().
And in fact you already did this? I see another series which resends
this patch as 1/5.
Oleg.
next prev parent reply other threads:[~2014-02-24 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ae3d74e79649d9e4962d0da030fb4852ddc5b8d1.1387227114.git.rgb@redhat.com>
[not found] ` <cover.1390495874.git.rgb@redhat.com>
2014-01-23 19:32 ` [PATCH 7/7] pid: get pid_t ppid of task in init_pid_ns Richard Guy Briggs
2014-02-20 19:01 ` Oleg Nesterov
2014-02-21 18:10 ` Richard Guy Briggs
2014-02-24 18:32 ` Oleg Nesterov [this message]
2014-03-17 20:14 ` Tony Luck
2014-03-17 20:15 ` Eric Paris
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=20140224183232.GA21474@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rgb@redhat.com \
--cc=stable@vger.kernel.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).