From: Roland McGrath <roland@redhat.com>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Austin Clements <amdragon+kernelbugzilla@mit.edu>,
Ingo Molnar <mingo@elte.hu>, john stultz <johnstul@us.ibm.com>,
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: Thu, 22 May 2008 14:50:57 -0700 (PDT) [thread overview]
Message-ID: <20080522215057.DCDF326FA24@magilla.localdomain> (raw)
In-Reply-To: Oleg Nesterov's message of Thursday, 22 May 2008 15:12:11 +0400 <20080522111211.GA117@tv-sign.ru>
> This is not enough. Again, we remove and free sigqueue but don't discard
> the pending signal. (and we must take into account other rt signals with
> the same si_signo if we want to discard the signal).
Right, of course. The sigset_t collecting while checking the queue is the
only way to do it. Note that you need to make it:
if (q->info.si_code == SI_TIMER && sig >= SIGRTMIN)
because a SI_TIMER could be using a legacy_queue signal number. In that
case there might have been a second non-timer signal pending with that
number too, which must not get cleared. Since the only siginfo_t still
recorded is the SI_TIMER one, better to leave it queued than turn it into
an infoless signal, seems to me.
Thanks,
Roland
next prev parent reply other threads:[~2008-05-22 21:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 15:14 Oleg Nesterov
2008-05-21 2:20 ` Roland McGrath
2008-05-21 11:54 ` Oleg Nesterov
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 [this message]
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=20080522215057.DCDF326FA24@magilla.localdomain \
--to=roland@redhat.com \
--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=oleg@tv-sign.ru \
--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
all inboxes | Powered by JetHome®