From: Jakub Kicinski <kuba@kernel.org>
To: Xiang Mei <xmei5@asu.edu>
Cc: Allison Henderson <achender@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
rds-devel@oss.oracle.com, linux-kernel@vger.kernel.org,
Santosh Shilimkar <santosh.shilimkar@oracle.com>,
Ka-Cheong Poon <ka-cheong.poon@oracle.com>,
bestswngs@gmail.com
Subject: Re: [PATCH net v3] rds: tcp: hold the RCU lock across ipv6_chk_addr() in rds_tcp_laddr_check()
Date: Wed, 22 Jul 2026 11:27:19 -0700 [thread overview]
Message-ID: <20260722112719.17665461@kernel.org> (raw)
In-Reply-To: <20260714212239.1511269-1-xmei5@asu.edu>
On Tue, 14 Jul 2026 14:22:39 -0700 Xiang Mei wrote:
> Changes since v1:
> Use rcu_read_locks instead of dev_hold/put
> Rebased on [PATCH net v2] rds: Fix inet6_addr_lst NULL dereference when IPv6 is disabled
>
> Changes since v2:
> Add change log
Why did you(r LLM) leave this portion of the change log in here and the
rest in the correct place below?
> Fixes: eee2fa6ab322 ("rds: Changing IP address internal representation to struct in6_addr")
> Reported-by: Weiming Shi <bestswngs@gmail.com>
> Assisted-by: Claude:claude-opus-4-8
> Signed-off-by: Xiang Mei <xmei5@asu.edu>
> Reviewed-by: Allison Henderson <achender@kernel.org>
> ---
> v2: Use rcu_read_locks and rebase on rds: Fix inet6_addr_lst NULL
> dereference when IPv6 is disabled
> v3: Add change log to commit message as Allison suggested
The patch does not apply, if it's still relevant please rebase and
repost.
--
pw-bot: cr
next prev parent reply other threads:[~2026-07-22 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 21:22 [PATCH net v3] rds: tcp: hold the RCU lock across ipv6_chk_addr() in rds_tcp_laddr_check() Xiang Mei
2026-07-22 18:27 ` Jakub Kicinski [this message]
2026-07-22 20:07 ` Xiang Mei
2026-07-22 21:04 ` Xiang Mei
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=20260722112719.17665461@kernel.org \
--to=kuba@kernel.org \
--cc=achender@kernel.org \
--cc=bestswngs@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=ka-cheong.poon@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@oracle.com \
--cc=xmei5@asu.edu \
/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