From: ebiederm@xmission.com (Eric W. Biederman)
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] worker_thread: don't play with SIGCHLD
Date: Fri, 13 Apr 2007 07:21:49 -0600 [thread overview]
Message-ID: <m1irc0pfyq.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20070413072910.GA1522@tv-sign.ru> (Oleg Nesterov's message of "Fri, 13 Apr 2007 11:29:10 +0400")
Oleg Nesterov <oleg@tv-sign.ru> writes:
> depends on Eric's
>
> kthread-dont-depend-on-work-queues-take-2.patch
>
> worker_thread() inherits ignored SIGCHLD from its parent, kthreadd.
> We can remove unneeded do_sigaction().
Acked-by: "Eric W. Biederman" <ebiederm@xmission.com>
Looks good.
We could delete all of:
> set_user_nice(current, -5);
>
> /* Block and flush all signals */
> sigfillset(&blocked);
> sigprocmask(SIG_BLOCK, &blocked, NULL);
> flush_signals(current);
>
> /*
> * We inherited MPOL_INTERLEAVE from the booting kernel.
> * Set MPOL_DEFAULT to insure node local allocations.
> */
> numa_default_policy();
>
> /* SIG_IGN makes children autoreap: see do_notify_parent(). */
> sa.sa.sa_handler = SIG_IGN;
> sa.sa.sa_flags = 0;
> siginitset(&sa.sa.sa_mask, sigmask(SIGCHLD));
> do_sigaction(SIGCHLD, &sa, (struct k_sigaction *)0);
If we wanted to, as that all comes by default from kthreadd.
Eric
next prev parent reply other threads:[~2007-04-13 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 7:29 Oleg Nesterov
2007-04-13 13:21 ` Eric W. Biederman [this message]
2007-04-13 13:40 ` Oleg Nesterov
2007-04-13 13:54 ` [PATCH] worker_thread: don't play with SIGCHLD and numa policy Oleg Nesterov
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=m1irc0pfyq.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
/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®