From: Oleg Nesterov <oleg@tv-sign.ru>
To: Roland McGrath <roland@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Austin Clements <amdragon+kernelbugzilla@mit.edu>,
Ingo Molnar <mingo@elte.hu>, john stultz <johnstul@us.ibm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Michael Kerrisk <mtk.manpages@googlemail.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] signals: sigqueue_free: don't free sigqueue if it is queued
Date: Wed, 21 May 2008 15:54:14 +0400 [thread overview]
Message-ID: <20080521115414.GA147@tv-sign.ru> (raw)
In-Reply-To: <20080521022046.1501F26FA1C@magilla.localdomain>
On 05/20, Roland McGrath wrote:
>
> > This patch doesn't change the behaviour of sys_timer_delete() and friends,
> > just makes it more correct and allows us to introduce other SIGQUEUE_ flags
> > passed to the receiver.
>
> To clarify, this certainly does change the behavior.
> There are two changes.
>
> Firstly, a pending timer-firing signal currently gets its siginfo_t
> zeroed out synchronously by timer_delete and now will have its info
> preserved. That change alone is a potential problem for userland, so
> it should not go in without the following changes to prevent userland
> from seeing the signal at all. (Currently userland may see a spurious
> signal, but its si_code and si_value don't indicate a timer firing.
> With the correct info, userland might try to use a pointer from
> si_value that was freed around the time it called timer_delete.)
Yes, yes, I meant doesn't change the behaviour in a sense that the
signal is still "visible" to the application.
> Second, a pending timer-firing signal currently stops counting towards
> the RLIMIT_SIGPENDING limit immediately upon a timer_delete call and
> now will keep counting toward that limit until it gets dequeued and
> discarded. This change is not necessarily a problem. (POSIX does not
> specify how we decide when resources are too short to create a new
> timer or queue a signal.) But it deserves mention somewhere.
> Applications can just get fixed to always unblock the signal number or
> flush old signals out with sigwait, if they are averse to timer
> signals with intact siginfo_t arriving after timer_delete.
Yes, thanks, I didn't think about this.
> For this reason, I don't think this set of changes should be
> considered for any -stable branch.
Yes sure.
> > q->flags |= SIGQUEUE_CANCELLED;
> > spin_lock_irqsave(lock, flags);
> > q->flags &= ~SIGQUEUE_PREALLOC;
>
> Just make it:
>
> spin_lock_irqsave(lock, flags);
> q->flags |= SIGQUEUE_CANCELLED;
> q->flags &= ~SIGQUEUE_PREALLOC;
>
> and we needn't wax philosophical about the meaning of locking rules. That
> patch would have my ACK, but I concur with Linus about the undesireability
> of the plain = version.
OK, will do tomorrow, but...
Oh well. I just realized SIGQUEUE_CANCELLED breaks sys_sigpending() ?
Oleg.
next prev parent reply other threads:[~2008-05-21 12:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 15:14 [PATCH 1/3] signals: sigqueue_free: don't free sigqueue if it is queued Oleg Nesterov
2008-05-21 2:20 ` Roland McGrath
2008-05-21 11:54 ` Oleg Nesterov [this message]
2008-05-21 18:42 ` Roland McGrath
2008-05-21 18:49 ` Linus Torvalds
2008-05-21 19:33 ` Roland McGrath
2008-05-21 20:07 ` Linus Torvalds
2008-05-21 23:01 ` Roland McGrath
2008-05-22 11:12 ` Oleg Nesterov
2008-05-22 11:55 ` Oleg Nesterov
2008-05-22 21:50 ` Roland McGrath
2008-05-22 21:18 ` Oleg Nesterov
2008-05-23 1:41 ` Roland McGrath
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=20080521115414.GA147@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@linux-foundation.org \
--cc=amdragon+kernelbugzilla@mit.edu \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtk.manpages@googlemail.com \
--cc=roland@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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