public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] signals: don't copy siginfo_t on dequeue
Date: Thu, 26 Feb 2009 20:15:09 +0100	[thread overview]
Message-ID: <20090226191509.GA6204@redhat.com> (raw)
In-Reply-To: <20090226184433.GA15644@damson.getinternet.no>

On 02/26, Vegard Nossum wrote:
>
> Instead of copying the siginfo_t whenever a signal is dequeued, just
> get the pointer to the struct sigqueue, which can be freed by the
> caller when the signal has been delivered.

Yes, it would bi nice. But it is not that simple,

> -static void collect_signal(int sig, struct sigpending *list, siginfo_t *info)
> +static struct sigqueue *collect_signal(int sig, struct sigpending *list)
>  {
>  	struct sigqueue *q, *first = NULL;
>  
> @@ -377,40 +377,29 @@ static void collect_signal(int sig, struct sigpending *list, siginfo_t *info)
>  	if (first) {
>  still_pending:
>  		list_del_init(&first->list);
> -		copy_siginfo(info, &first->info);
> -		__sigqueue_free(first);
> -	} else {
> -		/* Ok, it wasn't in the queue.  This must be
> -		   a fast-pathed signal or we must have been
> -		   out of queue space.  So zero out the info.
> -		 */
> -		info->si_signo = sig;
> -		info->si_errno = 0;
> -		info->si_code = 0;
> -		info->si_pid = 0;
> -		info->si_uid = 0;
>  	}
> +
> +	return first;
>  }
>  
> -static int __dequeue_signal(struct sigpending *pending, sigset_t *mask,
> -			siginfo_t *info)
> +static struct sigqueue *__dequeue_signal(struct sigpending *pending,
> +	sigset_t *mask)
>  {
>  	int sig = next_signal(pending, mask);
>  
> -	if (sig) {
> -		if (current->notifier) {
> -			if (sigismember(current->notifier_mask, sig)) {
> -				if (!(current->notifier)(current->notifier_data)) {
> -					clear_thread_flag(TIF_SIGPENDING);
> -					return 0;
> -				}
> +	if (!sig)
> +		return NULL;
> +
> +	if (current->notifier) {
> +		if (sigismember(current->notifier_mask, sig)) {
> +			if (!(current->notifier)(current->notifier_data)) {
> +				clear_thread_flag(TIF_SIGPENDING);
> +				return 0;
>  			}
>  		}
> -
> -		collect_signal(sig, pending, info);
>  	}
>  
> -	return sig;
> +	return collect_signal(sig, pending);

So. dequeue_signal() returns NULL if there is no siginfo queued. In that
case we assume that the signal is not pending.

But this is not right. Think about SEND_SIG_FORCED, or __sigqueue_alloc()
failure when the signal is sent. Or look at zap_other_threads() for example,
it just sets the bit in ->pending but doesn't queue siginfo.

Oleg.


  parent reply	other threads:[~2009-02-26 19:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-26 18:44 [RFC][PATCH] signals: don't copy siginfo_t on dequeue Vegard Nossum
2009-02-26 18:50 ` Ingo Molnar
2009-02-26 19:10   ` Vegard Nossum
2009-02-26 20:19     ` Oleg Nesterov
2009-02-26 20:27       ` Ingo Molnar
2009-02-26 19:15 ` Oleg Nesterov [this message]
2009-02-26 20:18   ` Vegard Nossum
2009-02-26 20:36     ` Oleg Nesterov

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=20090226191509.GA6204@redhat.com \
    --to=oleg@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    --cc=vegard.nossum@gmail.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