netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Anjali Kulkarni <anjali.k.kulkarni@oracle.com>
Cc: davem@davemloft.net, Liam.Howlett@Oracle.com,
	edumazet@google.com, pabeni@redhat.com, mingo@redhat.com,
	peterz@infradead.org, juri.lelli@redhat.com,
	vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
	rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
	vschneid@redhat.com, jiri@resnulli.us,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	akpm@linux-foundation.org, shuah@kernel.org,
	linux-kselftest@vger.kernel.org, peili.io@oracle.com
Subject: Re: [PATCH net-next v1 0/3] Threads support in proc connector
Date: Tue, 15 Oct 2024 09:01:48 -0700	[thread overview]
Message-ID: <20241015090148.72e83f7f@kernel.org> (raw)
In-Reply-To: <20241013170617.2139204-1-anjali.k.kulkarni@oracle.com>

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

  parent reply	other threads:[~2024-10-15 16:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-13 17:06 [PATCH net-next v1 0/3] Threads support in proc connector Anjali Kulkarni
2024-10-13 17:06 ` [PATCH net-next v1 1/3] connector/cn_proc: Add hash table for threads Anjali Kulkarni
2024-10-14  8:27   ` Peter Zijlstra
2024-10-14 15:52     ` Anjali Kulkarni
2024-10-13 17:06 ` [PATCH net-next v1 2/3] connector/cn_proc: Kunit tests for threads hash table Anjali Kulkarni
2024-10-13 17:06 ` [PATCH net-next v1 3/3] connector/cn_proc: Selftest for threads Anjali Kulkarni
2024-10-15 16:01 ` Jakub Kicinski [this message]
2024-10-15 16:22   ` [PATCH net-next v1 0/3] Threads support in proc connector Anjali Kulkarni
2024-10-15 16:48     ` Jakub Kicinski
2024-10-15 16:53       ` Anjali Kulkarni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241015090148.72e83f7f@kernel.org \
    --to=kuba@kernel.org \
    --cc=Liam.Howlett@Oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=anjali.k.kulkarni@oracle.com \
    --cc=bsegall@google.com \
    --cc=davem@davemloft.net \
    --cc=dietmar.eggemann@arm.com \
    --cc=edumazet@google.com \
    --cc=jiri@resnulli.us \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=peili.io@oracle.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=shuah@kernel.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).