From: Jakub Kicinski <kuba@kernel.org>
To: Maoyi Xie <maoyixie.tju@gmail.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Allison Henderson <achender@kernel.org>,
Praveen Kakkolangara <praveen.kakkolangara@aumovio.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
rds-devel@oss.oracle.com, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH net v5] rds: filter RDS_INFO_* getsockopt by caller's netns
Date: Tue, 19 May 2026 18:55:37 -0700 [thread overview]
Message-ID: <20260519185537.772bf34c@kernel.org> (raw)
In-Reply-To: <20260518174613.1592290-1-maoyixie.tju@gmail.com>
On Tue, 19 May 2026 01:46:13 +0800 Maoyi Xie wrote:
> The RDS_INFO_* family of getsockopt(2) options reads several
> file-scope global lists that are not per-netns:
>
> rds_sock_info / rds6_sock_info,
> rds_sock_inc_info / rds6_sock_inc_info -> rds_sock_list
> rds_tcp_tc_info / rds6_tcp_tc_info -> rds_tcp_tc_list
> rds_conn_info / rds6_conn_info,
> rds_conn_message_info_cmn (for the *_SEND_MESSAGES and
> *_RETRANS_MESSAGES variants),
> rds_for_each_conn_info (for RDS_INFO_IB_CONNECTIONS)
> -> rds_conn_hash[]
Does not apply to net:
Applying: rds: filter RDS_INFO_* getsockopt by caller's netns
error: patch failed: net/rds/tcp.c:201
error: net/rds/tcp.c: patch does not apply
Patch failed at 0001 rds: filter RDS_INFO_* getsockopt by caller's netns
--
pw-bot: cr
prev parent reply other threads:[~2026-05-20 1:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 17:46 [PATCH net v5] rds: filter RDS_INFO_* getsockopt by caller's netns Maoyi Xie
2026-05-20 1:55 ` Jakub Kicinski [this message]
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=20260519185537.772bf34c@kernel.org \
--to=kuba@kernel.org \
--cc=achender@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=maoyixie.tju@gmail.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=pabeni@redhat.com \
--cc=praveen.kakkolangara@aumovio.com \
--cc=rds-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.