netdev - Re: [PATCH net-next v1 0/3] Threads support in proc connector

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: <20241015090148.72e83f7f@kernel.org>
Date: Tue, 15 Oct 2024 09:01:48 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Anjali Kulkarni <anjali.k.kulkarni@...cle.com>
Cc: davem@...emloft.net, Liam.Howlett@...cle.com, edumazet@...gle.com,
 pabeni@...hat.com, mingo@...hat.com, peterz@...radead.org,
 juri.lelli@...hat.com, vincent.guittot@...aro.org,
 dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com,
 mgorman@...e.de, vschneid@...hat.com, jiri@...nulli.us,
 linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
 akpm@...ux-foundation.org, shuah@...nel.org,
 linux-kselftest@...r.kernel.org, peili.io@...cle.com
Subject: Re: [PATCH net-next v1 0/3] Threads support in proc connector

On Sun, 13 Oct 2024 10:06:14 -0700 Anjali Kulkarni wrote:
> However, for threads, when it does a pthread_exit(&exit_status) call, the
> kernel is not aware of the exit status with which pthread_exit is called.
> It is sent by child thread to the parent process, if it is waiting in
> pthread_join(). Hence, for a thread exiting abnormally, kernel cannot
> send notifications to any listening processes.

I really don't think this should be going via networking.
We can help review the netlink bits, if any, but otherwise we are far
outside of our comfort zone. 

IOW when you repost please drop the net-next designation and you'll
need to find someone else to merge these patches, or send a PR directly
to Linus himself during the merge window.
-- 
pw-bot: nap