From: Thomas Gleixner <tglx@linutronix.de>
To: John <me@privacy.net>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, johnstul@us.ibm.com,
akpm@osdl.org
Subject: Re: Incorrect behavior of timer_settime() for absolute dates in the past
Date: Thu, 30 Nov 2006 14:26:01 +0100 [thread overview]
Message-ID: <1164893161.6242.4.camel@localhost> (raw)
In-Reply-To: <455D7CDD.9000202@privacy.net>
On Fri, 2006-11-17 at 10:11 +0100, John wrote:
> value specified by the it_value member of value. If the specified time
> has already passed, the function shall succeed and the expiration
> notification shall be made."
That's exactly what the implementation does:
The functions succeeds (return value is 0) and then the notification is
made. There is _NO_ requirement that the signal is delivered before the
function returns to user space. I could be implemented, but I'm not sure
if it is worth the effort.
tglx
prev parent reply other threads:[~2006-11-30 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 9:11 Incorrect behavior of timer_settime() for absolute dates in the past John
2006-11-27 14:32 ` John
2006-11-28 2:09 ` Andrew Morton
2006-11-30 13:26 ` Thomas Gleixner [this message]
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=1164893161.6242.4.camel@localhost \
--to=tglx@linutronix.de \
--cc=akpm@osdl.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=me@privacy.net \
--cc=mingo@elte.hu \
/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