From: akpm@linux-foundation.org
To: vandebo-lkml@NerdBox.Net, mingo@elte.hu, oleg@tv-sign.ru,
roland@redhat.comvandebo-lkml@NerdBox.Net,
mm-commits@vger.kernel.org
Subject: - exit-signals-use-of-uninitialized-field-notify_count.patch removed from -mm tree
Date: Tue, 02 Sep 2008 12:48:29 -0700 [thread overview]
Message-ID: <200809021948.m82JmTiL009545@imap1.linux-foundation.org> (raw)
The patch titled
exit signals: use of uninitialized field notify_count
has been removed from the -mm tree. Its filename was
exit-signals-use-of-uninitialized-field-notify_count.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: exit signals: use of uninitialized field notify_count
From: Steve VanDeBogart <vandebo-lkml@NerdBox.Net>
task->signal->notify_count is only initialized if
task->signal->group_exit_task is not NULL. Reorder a conditional so
that uninitialised memory is not used. Found by Valgrind.
Signed-off-by: Steve VanDeBogart <vandebo-lkml@nerdbox.net>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Roland McGrath <roland@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/exit.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN kernel/exit.c~exit-signals-use-of-uninitialized-field-notify_count kernel/exit.c
--- a/kernel/exit.c~exit-signals-use-of-uninitialized-field-notify_count
+++ a/kernel/exit.c
@@ -918,8 +918,8 @@ static void exit_notify(struct task_stru
/* mt-exec, de_thread() is waiting for us */
if (thread_group_leader(tsk) &&
- tsk->signal->notify_count < 0 &&
- tsk->signal->group_exit_task)
+ tsk->signal->group_exit_task &&
+ tsk->signal->notify_count < 0)
wake_up_process(tsk->signal->group_exit_task);
write_unlock_irq(&tasklist_lock);
_
Patches currently in -mm which might be from vandebo-lkml@NerdBox.Net are
reply other threads:[~2008-09-02 19:50 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=200809021948.m82JmTiL009545@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=roland@redhat.comvandebo-lkml \
--cc=vandebo-lkml@NerdBox.Net \
/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