linux-kernel - Re: [RESEND PATCH] prctl: add PR_[GS]ET_PDEATHSIG

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: <CA+55aFwnx9rY435UT4qiYMWyL++DL2tVaeph-syrkVUrUCW=Xg@mail.gmail.com>
Date:   Tue, 3 Oct 2017 13:02:00 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     "Eric W. Biederman" <ebiederm@...ssion.com>
Cc:     Jürg Billeter <j@...ron.ch>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Oleg Nesterov <oleg@...hat.com>,
        Michael Kerrisk <mtk.manpages@...il.com>,
        Filipe Brandenburger <filbranden@...gle.com>,
        David Wilcox <davidvsthegiant@...il.com>, hansecke@...il.com,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RESEND PATCH] prctl: add PR_[GS]ET_PDEATHSIG_PROC

On Tue, Oct 3, 2017 at 12:30 PM, Eric W. Biederman
<ebiederm@...ssion.com> wrote:
>
> We never signal the orignal parent.  We signal the child that
> requested the pdeath_signal when the original parent dies.

Yeah, I keep making that mistake, because I always confuse this with
the exit_signal handling.

Just mentally kick me next time I do that: "Christ, Linus, not
*again*! Take your damn meds"

Anyway, it's more the "another confusing and fragile special case that
will probably not be used very widely and cause confusion because it
lacks any test coverage" thing I worry about most.

                   Linus