From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] exec: Only allow a threaded init to exec from the thread_group_leader
Date: Sun, 29 Jan 2006 03:25:32 -0700 [thread overview]
Message-ID: <m1irs38h5v.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20060129003606.7887ecd9.akpm@osdl.org> (Andrew Morton's message of "Sun, 29 Jan 2006 00:36:06 -0800")
Andrew Morton <akpm@osdl.org> writes:
>> 408dad0f2b7067b23929866150e73b2b2f12d662
>> diff --git a/fs/exec.c b/fs/exec.c
>> index 055378d..c9d8e31 100644
>> --- a/fs/exec.c
>> +++ b/fs/exec.c
>> @@ -600,6 +600,12 @@ static int de_thread(struct task_struct
>> if (thread_group_empty(current))
>> goto no_thread_group;
>>
>> + /* A threaded init must exec from it's primary thread.
>> + * As the init task (i.e. child_reaper) may not exit.
>> + */
>> + if (!thread_group_leader(current) && (current->tgid == 1))
>> + return -EINVAL;
>> +
>> /*
>> * Kill all other threads in the thread group.
>> * We must hold tasklist_lock to call zap_other_threads.
>
> hmm, this just looks like overhead. If sometime someone _does_ try to
> thread init, what will happen to them? If it's something nice and nasty,
> they'll just whine at us and stop doing that. Same net effect, no runtime
> cost.
So threading init will work just fine. The only case that will blow up
is calling exec from something that is not the thread group leader.
i.e. If tgid == 1 but pid != 1 the kernel will cause pid == 1 to exit.
I think that will trigger a kernel panic. It might just ensure that
no more processes are re-parented to init. And we dereference a
bad pointer we look at child_reaper. I haven't been brave enough
to try it.
The cost is only paid if you are a threaded task and you call exec.
Normal process never take that path, so we are already off of the
fast path.
The test when all expanded out is only:
if ((current->tgid == current->pid) && (current->tgid == 1))
return -EINVAL
So it should be relatively cheap.
If process id namespaces become a reality init stops being
terribly special, and becomes something you may have several
of running at any one time. If one of those inits is compromised
by a hostile user I having the whole system go down so we can
avoid executing a cheap test sounds terribly wrong. That is
why I really care.
Eric
next prev parent reply other threads:[~2006-01-29 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 6:18 Eric W. Biederman
2006-01-29 8:36 ` Andrew Morton
2006-01-29 10:25 ` Eric W. Biederman [this message]
2006-01-29 10:48 ` Andrew Morton
2006-01-29 15:24 ` Pavel Machek
2006-01-29 19:32 ` Andrew Morton
2006-01-29 21:32 ` Eric W. Biederman
2006-01-30 9:15 ` Jan Engelhardt
2006-01-30 20:41 ` Eric W. Biederman
[not found] <5AeeD-7xb-7@gated-at.bofh.it>
[not found] ` <5Aggm-1V6-3@gated-at.bofh.it>
[not found] ` <5AhYT-4uR-7@gated-at.bofh.it>
2006-01-29 13:36 ` Bodo Eggert
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=m1irs38h5v.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®