mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Namhyung Kim <namhyung@gmail.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
	Roland McGrath <roland@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] signal: annotate siglock acquisition
Date: Sat, 25 Sep 2010 11:42:07 +0200	[thread overview]
Message-ID: <1285407727.2478.288.camel@edumazet-laptop> (raw)
In-Reply-To: <1285406495-20080-1-git-send-email-namhyung@gmail.com>

Le samedi 25 septembre 2010 à 18:21 +0900, Namhyung Kim a écrit :
> 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.

> @@ -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 */

making sparse happy is good, but changing a likely clause is not,
unless you meant it ;)

maybe -->

	if (!likely(lock_task_sighand(t, &flags)))
		goto ret;
	else
		__acquire(&t->sighand->siglock);




  reply	other threads:[~2010-09-25  9:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-25  9:21 Namhyung Kim
2010-09-25  9:42 ` Eric Dumazet [this message]
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=1285407727.2478.288.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@gmail.com \
    --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®