linux-kernel - Re: [patch 1/4] signalfd v1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <45EF392F.5070101@goop.org>
Date:	Wed, 07 Mar 2007 14:14:07 -0800
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Davide Libenzi <davidel@...ilserver.org>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [patch 1/4] signalfd v1 - signalfd core ...

Davide Libenzi wrote:
> You have the *choice* to do that:
>
> 1) You want standard delivery only:
>
>    - Just dont use signalfd
>
> 2) you want signalfd only:
>
>    - Do a sigprocmask(SIG_BLOCK) of the same mask you pass to signalfd
>
> If you want both, you can have it. Race free.
>   

It's only usefully race-free if you are guarantee that each signal gets
delivered once, by one path or the other.  Otherwise you get a
non-deterministic number of each signal actually delivered - what
earthly use is that to an application?

    J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/