From: Christian Brauner <brauner@kernel.org>
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: alexander@mihalicyn.com, bluca@debian.org,
daan.j.demeyer@gmail.com, davem@davemloft.net,
david@readahead.eu, edumazet@google.com, horms@kernel.org,
jack@suse.cz, kuba@kernel.org, lennart@poettering.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
me@yhndnzj.com, netdev@vger.kernel.org, oleg@redhat.com,
pabeni@redhat.com
Subject: Re: [PATCH RFC 2/4] net, pidfs: prepare for handing out pidfds for reaped sk->sk_peer_pid
Date: Fri, 25 Apr 2025 10:02:20 +0200 [thread overview]
Message-ID: <20250425-richten-hubschrauber-02bba42aa559@brauner> (raw)
In-Reply-To: <20250425011448.86924-1-kuniyu@amazon.com>
> I prefer DEBUG_NET_WARN_ON_ONCE() or removing it as rcu_sleep_check()
I've removed it.
next prev parent reply other threads:[~2025-04-25 8:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 12:24 [PATCH RFC 0/4] net, pidfs: enable handing out pidfds for reaped sk->sk_peer_pid Christian Brauner
2025-04-24 12:24 ` [PATCH RFC 1/4] pidfs: register pid in pidfs Christian Brauner
2025-04-24 13:24 ` Oleg Nesterov
2025-04-24 15:19 ` Christian Brauner
2025-04-24 12:24 ` [PATCH RFC 2/4] net, pidfs: prepare for handing out pidfds for reaped sk->sk_peer_pid Christian Brauner
2025-04-24 12:44 ` David Rheinsberg
2025-04-24 15:19 ` Christian Brauner
2025-04-25 1:08 ` Kuniyuki Iwashima
2025-04-25 8:02 ` Christian Brauner [this message]
2025-04-25 1:57 ` Kuniyuki Iwashima
2025-04-25 7:58 ` Christian Brauner
2025-04-24 12:24 ` [PATCH RFC 3/4] pidfs: get rid of __pidfd_prepare() Christian Brauner
2025-04-24 12:24 ` [PATCH RFC 4/4] net, pidfs: enable handing out pidfds for reaped sk->sk_peer_pid Christian Brauner
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=20250425-richten-hubschrauber-02bba42aa559@brauner \
--to=brauner@kernel.org \
--cc=alexander@mihalicyn.com \
--cc=bluca@debian.org \
--cc=daan.j.demeyer@gmail.com \
--cc=davem@davemloft.net \
--cc=david@readahead.eu \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jack@suse.cz \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=lennart@poettering.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@yhndnzj.com \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pabeni@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