From: Peter Hurley <peter@hurleysoftware.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Sree Harsha Totakura <sreeharsha@totakura.in>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: pppd service crash in linux-3.13.6
Date: Fri, 14 Mar 2014 16:28:18 -0400 [thread overview]
Message-ID: <53236662.3020707@hurleysoftware.com> (raw)
In-Reply-To: <20140314192346.GA14823@redhat.com>
On 03/14/2014 03:23 PM, Oleg Nesterov wrote:
> On 03/14, Peter Hurley wrote:
>>
>>> On 03/13/2014 01:06 PM, Oleg Nesterov wrote:
>>>>
>>>> OTOH, why we should delay disassociate_ctty? IOW, do you see any
>>>> potential problem with the trivial patch below?
>>
>> Won't work.
>>
>> cgroup_exit() can exec a userspace process (the notify_on_exit() facility)
> ^^^^^^^^^^^^^^^^
>
> can't find anything named notify_on_exit, perhap you meant
> cgroup_release_agent? Although I guess this should not matter.
Sorry, I meant the notify_on_release() facility as discussed in the
function header comments of cgroup_exit().
Yes, cgroup_release_agent() is the work function that is scheduled.
>> which requires both namespace and tty facilities.
>
> Hmm... why?
>
> The exiting task obviously can't exec. The only way to spawn a userspace
> process is call_usermodehelper(), it should work just fine, no?
You're correct, in the immediate sense that the user command exec'd will
not inherit open file descriptors.
But what if it expects to be able to find the intact children of
the foreground process group, and can't because the controlling tty
has already been torn down and all the children already sent SIGHUP.
I know that's not what the user command is intended for, but
userspace can be enterprising for establishing dependencies on
kernel constructs.
Or what if the user command expects to find and join the user namespace
of the dying process but now it's already been freed?
Regards,
Peter Hurley
next prev parent reply other threads:[~2014-03-14 20:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 21:19 pppd service crash in linux-3.13.6 Sree Harsha Totakura
2014-03-10 16:56 ` Sree Harsha Totakura
2014-03-10 19:23 ` Peter Hurley
2014-03-13 17:06 ` Oleg Nesterov
2014-03-13 17:55 ` Peter Hurley
2014-03-14 14:19 ` Peter Hurley
2014-03-14 15:02 ` Peter Hurley
2014-03-14 19:23 ` Oleg Nesterov
2014-03-14 20:28 ` Peter Hurley [this message]
2014-03-14 21:04 ` Oleg Nesterov
2014-03-15 12:49 ` Peter Hurley
2014-03-17 18:04 ` [PATCH 0/2] (Was: pppd service crash in linux-3.13.6) Oleg Nesterov
2014-03-17 18:04 ` [PATCH 1/2] exit: call disassociate_ctty() before exit_task_namespaces() Oleg Nesterov
2014-03-17 18:05 ` [PATCH 2/2] exit: move check_stack_usage() to the end of do_exit() Oleg Nesterov
2014-03-10 19:54 ` pppd service crash in linux-3.13.6 Ben Hutchings
2014-03-12 21:25 ` Sree Harsha Totakura
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=53236662.3020707@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=sreeharsha@totakura.in \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.