From: Matthieu CASTET <matthieu.castet@parrot.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] signals: real-time signals delivery order
Date: Wed, 11 Jul 2007 07:34:14 +0000 (UTC) [thread overview]
Message-ID: <loom.20070711T092936-151@post.gmane.org> (raw)
In-Reply-To: 1184116335.19893.12.camel@localhost
Anton Salikhmetov <salikhmetov <at> gmail.com> writes:
>
> From: Anton Salikhmetov <salikhmetov <at> gmail.com>
>
> According to the POSIX standard, multiple real-time signals
> pending to a process should be delivered in a strict order.
> Specifically, the lowest-numbered signal should be delivered
> first and multiple occurrences of signals with the same number
> should be delivered in FIFO order.
>
> Current Linux kernel delivers the highest-numbered signals
> pending to a process first, not the lowest-numbered ones. This
> contradicts to the requirement explained above. The problem can
> be demonstrated by the following test program:
I believe you should check that you mask or signal in your signal handler.
If you don't the high-prio handler will be prempted by low-prio, and they will
be executed in the reverse order.
Matthieu
next prev parent reply other threads:[~2007-07-11 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 1:12 [PATCH] signals: real-time signals delivery order Anton Salikhmetov
2007-07-11 7:34 ` Matthieu CASTET [this message]
2007-07-11 9:10 ` Anton Salikhmetov
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=loom.20070711T092936-151@post.gmane.org \
--to=matthieu.castet@parrot.com \
--cc=linux-kernel@vger.kernel.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