From: Namhyung Kim <namhyung@gmail.com>
To: Oleg Nesterov <oleg@redhat.com>, Roland McGrath <roland@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] signal: annotate siglock acquisition
Date: Sat, 25 Sep 2010 18:21:35 +0900 [thread overview]
Message-ID: <1285406495-20080-1-git-send-email-namhyung@gmail.com> (raw)
lock_task_sighand() conditionally acquires sighand->siglock in case of
returning non-NULL but unlock_task_sighand() releases it unconditionally.
This leads sparse to complain about the lock context imbalance. Annotate it
to make sparse happier.
Signed-off-by: Namhyung Kim <namhyung@gmail.com>
---
kernel/signal.c | 9 ++++++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/kernel/signal.c b/kernel/signal.c
index bded651..85c1efd 100644
--- a/kernel/signal.c
+++ b/kernel/signal.c
@@ -1037,7 +1037,7 @@ int do_send_sig_info(int sig, struct siginfo *info, struct task_struct *p,
unsigned long flags;
int ret = -ESRCH;
- if (lock_task_sighand(p, &flags)) {
+ if (__cond_lock(&p->sighand->siglock, lock_task_sighand(p, &flags))) {
ret = send_signal(sig, info, p, group);
unlock_task_sighand(p, &flags);
}
@@ -1226,7 +1226,8 @@ int kill_pid_info_as_uid(int sig, struct siginfo *info, struct pid *pid,
goto out_unlock;
if (sig) {
- if (lock_task_sighand(p, &flags)) {
+ if (__cond_lock(&p->sighand->siglock,
+ lock_task_sighand(p, &flags))) {
ret = __send_signal(sig, info, p, 1, 0);
unlock_task_sighand(p, &flags);
} else
@@ -1403,7 +1404,9 @@ int send_sigqueue(struct sigqueue *q, struct task_struct *t, int group)
BUG_ON(!(q->flags & SIGQUEUE_PREALLOC));
ret = -1;
- if (!likely(lock_task_sighand(t, &flags)))
+ if (likely(lock_task_sighand(t, &flags)))
+ __acquire(&t->sighand->siglock);
+ else
goto ret;
ret = 1; /* the signal is ignored */
--
1.7.2.2
next reply other threads:[~2010-09-25 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 9:21 Namhyung Kim [this message]
2010-09-25 9:42 ` Eric Dumazet
2010-09-25 11:33 ` Namhyung Kim
2010-09-25 12:23 ` Eric Dumazet
2010-09-25 12:51 ` Namhyung Kim
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=1285406495-20080-1-git-send-email-namhyung@gmail.com \
--to=namhyung@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.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
all inboxes | Powered by JetHome®