Re: [PATCH] sigaction.2: setitimer(2)/alarm(2) timers yield si_code=SI_TIMER too

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jul 09, 2024 at 09:36:34PM GMT, наб wrote:
> On Tue, Jul 09, 2024 at 09:20:28PM +0200, Alejandro Colomar wrote:
> > On Tue, Jul 09, 2024 at 08:43:40PM GMT, наб wrote:
> > > On Tue, Jul 09, 2024 at 08:42:14PM +0200, Alejandro Colomar wrote:
> > > > On Tue, Jul 09, 2024 at 07:53:34PM GMT, наб wrote:
> > > > > On Tue, Jul 09, 2024 at 06:38:42PM +0200, Alejandro Colomar wrote:
> > > > > > On Mon, Jul 08, 2024 at 04:03:40AM GMT, наб wrote:
> > > > > > > Applies to Linux and NetBSD.
> > > > > > Is this non-standard behavior?
> > > > > In the case of setitimer(): "obviously yes" because the interface is
> > > > > not part of the standard.
> > > > The POSIX.1-2008 standard specifies setitimer(3p).
> > > But the current standard (-2024) doesn't.
> > Hmmm, do you want to send a patch for that?
> absolutely not, even the subset I have for voreutils was hell

No need to patch all pages.  Just the ones you want to.  I don't expect
anyone to update thosands of pages.  :)

> 
> > Anyway, for 2008, was it non-standard behavior?
> It wasn't "non-standard" so much as it was left up to the implementation
> (still is), except for timer_create().
> 
> All implementations agree here, so there's no point in splitting hair IMO

Okay.  Then, maybe, I'd remove the "Linux and NetBSD" bits from the
commit message, and just say something like all implementations do that?

Have a lovely night!
Alex

-- 
<https://www.alejandro-colomar.es/>

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux