From: Oleg Nesterov <oleg@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alan Cox <alan@linux.intel.com>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Roland McGrath <roland@redhat.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] make task_struct->signal stable
Date: Fri, 19 Mar 2010 19:40:13 +0100 [thread overview]
Message-ID: <20100319184013.GA504@redhat.com> (raw)
Depends on
[PATCH 1/4] exit: exit_notify() can trust signal->notify_count < 0
[PATCH 2/4] exit: change zap_other_threads() to count sub-threads
[PATCH 3/4] exit: avoid sig->count in de_thread/__exit_signal synchronization
[PATCH 4/4] exit: avoid sig->count in __exit_signal() to detect the group-dead case
[PATCH 1/2] posix-cpu-timers: avoid "task->signal != NULL" checks
[PATCH 2/2] ia64: ptrace_attach_sync_user_rbs: avoid "task->signal != NULL" checks
[PATCH] move tty_kref_put() outside of __cleanup_signal()
See the changelog in 1/3. IIRC, this was suggested by Ingo a long ago.
Note! This series is not complete, it needs some conclusive cleanups and
a lot more cleanups are possible because task->signal is never NULL. 3/3
is the "random" example.
Oleg.
reply other threads:[~2010-03-19 18:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100319184013.GA504@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=roland@redhat.com \
/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