linux-kernel - Re: Syscall kill() can send signal to thread ID

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]

Date:   Fri, 23 Sep 2022 09:53:30 +0200
From:   Florian Weimer <fweimer@...hat.com>
To:     cambda@...ux.alibaba.com
Cc:     "Eric W. Biederman" <ebiederm@...ssion.com>,
        linux-kernel@...r.kernel.org, linux-api@...r.kernel.org,
        Xuan Zhuo <xuanzhuo@...ux.alibaba.com>,
        Dust Li <dust.li@...ux.alibaba.com>,
        Tony Lu <tonylu@...ux.alibaba.com>
Subject: Re: Syscall kill() can send signal to thread ID

> I don't quite understand what you mean, sorry. But if kill() returns
> -ESRCH for tid which is not equal to tgid, kill() can only send signal
> to thread group via main thread id, that is what BSD did and manual
> said. It seems not odd?

It's still odd because there's one TID per process that's valid for
kill by accident.  That's all.

Thanks,
Florian