From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: namhyung@gmail.com, roland@redhat.com
Subject: + exit-add-lock-context-annotation-on-find_new_reaper.patch added to -mm tree
Date: Tue, 07 Sep 2010 15:16:08 -0700 [thread overview]
Message-ID: <201009072216.o87MG8gP009651@imap1.linux-foundation.org> (raw)
The patch titled
exit: add lock context annotation on find_new_reaper()
has been added to the -mm tree. Its filename is
exit-add-lock-context-annotation-on-find_new_reaper.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: exit: add lock context annotation on find_new_reaper()
From: Namhyung Kim <namhyung@gmail.com>
find_new_reaper() releases and regrabs tasklist_lock but was missing
proper annotations. Add it. This remove following sparse warning:
warning: context imbalance in 'find_new_reaper' - unexpected unlock
Signed-off-by: Namhyung Kim <namhyung@gmail.com>
Acked-by: Roland McGrath <roland@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/exit.c | 2 ++
1 file changed, 2 insertions(+)
diff -puN kernel/exit.c~exit-add-lock-context-annotation-on-find_new_reaper kernel/exit.c
--- a/kernel/exit.c~exit-add-lock-context-annotation-on-find_new_reaper
+++ a/kernel/exit.c
@@ -705,6 +705,8 @@ static void exit_mm(struct task_struct *
* space.
*/
static struct task_struct *find_new_reaper(struct task_struct *father)
+ __releases(&tasklist_lock)
+ __acquires(&tasklist_lock)
{
struct pid_namespace *pid_ns = task_active_pid_ns(father);
struct task_struct *thread;
_
Patches currently in -mm which might be from namhyung@gmail.com are
linux-next.patch
init-mark-__user-address-space-on-string-literals.patch
exit-add-lock-context-annotation-on-find_new_reaper.patch
reply other threads:[~2010-09-07 22:16 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=201009072216.o87MG8gP009651@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=namhyung@gmail.com \
--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