public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gernot Payer <gpayer@suse.de>
To: Chris Wright <chrisw@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Patch to disarm timers after an exec syscall
Date: Thu, 30 Jun 2005 10:27:57 +0200	[thread overview]
Message-ID: <200506301027.57380.gpayer@suse.de> (raw)
In-Reply-To: <20050629182725.GF9153@shell0.pdx.osdl.net>

On Wednesday 29 June 2005 20:27, Chris Wright wrote:
> No, this can't do.  It conflicts with the other bit of requirements.
> Specifically:
> http://www.opengroup.org/onlinepubs/009695399/functions/exec.html
>
> As you mention:
>
>   [TMR] Per-process timers created by the calling process
>   shall be deleted before replacing the current process image with the new
>   process image.
>
> But also:
>
>   The new process shall inherit at least the following attributes from the
>   calling process image:
>   <snip>
>   o [XSI] Interval timers
>
> And this kills the latter.

Ah, thanks for pointing that out. Unfortunately this fact isn't made clear in 
the timer_create page and the exec page isn't very understandable for 
non-native speakers and non-lawyers. ;-)

But after reading the parts you mentioned (expecially the [XSI] and [TMR] 
acronyms), I have to agree with you, the patch is wrong and so is the test 
case I mentioned.

However, poking around in the kernel was fun anyway. ;-)

> thanks,
> -chris

mfg
Gernot

      reply	other threads:[~2005-06-30  8:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29 12:55 Patch to disarm timers after an exec syscall Gernot Payer
2005-06-29 18:15 ` Andrew Morton
2005-06-29 18:31   ` Chris Wright
2005-06-29 18:50   ` Roland McGrath
2005-06-30  8:34     ` Gernot Payer
2005-06-29 18:27 ` Chris Wright
2005-06-30  8:27   ` Gernot Payer [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=200506301027.57380.gpayer@suse.de \
    --to=gpayer@suse.de \
    --cc=chrisw@osdl.org \
    --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