From: Allison Henderson <achender@kernel.org>
To: Jiayuan Chen <jiayuan.chen@linux.dev>, netdev@vger.kernel.org
Cc: syzbot+fbf3648ae7f5bdb05c59@syzkaller.appspotmail.com,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Andy Grover <andy.grover@oracle.com>,
linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] rds: annotate data-race around rs_seen_congestion
Date: Thu, 21 May 2026 21:49:19 -0700 [thread overview]
Message-ID: <ba093b6b93fffe07564e89dc5744efe45dfb4c21.camel@kernel.org> (raw)
In-Reply-To: <20260522011621.304470-1-jiayuan.chen@linux.dev>
On Fri, 2026-05-22 at 09:16 +0800, Jiayuan Chen wrote:
> rs_seen_congestion is read in rds_poll() and written in rds_sendmsg()
> and rds_poll() without any lock. Use READ_ONCE()/WRITE_ONCE() to
> annotate these lockless accesses and silence KCSAN.
>
> Fixes: b98ba52f96e7 ("RDS: only put sockets that have seen congestion on the poll_waitq")
> Reported-by: syzbot+fbf3648ae7f5bdb05c59@syzkaller.appspotmail.com
> Closes: https://lore.kernel.org/netdev/6a0f8d94.050a0220.6b33c.0000.GAE@google.com/
> Signed-off-by: Jiayuan Chen <jiayuan.chen@linux.dev>
Hi Jiayuan,
I was about to send the same patch, so no complaints here. Thanks for catching this.
Reviewed-by: Allison Henderson <achender@kernel.org>
Tested-by: Allison Henderson <achender@kernel.org>
Allison
> ---
> net/rds/af_rds.c | 4 ++--
> net/rds/send.c | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/net/rds/af_rds.c b/net/rds/af_rds.c
> index 76f625986a7f..93b2da63ed42 100644
> --- a/net/rds/af_rds.c
> +++ b/net/rds/af_rds.c
> @@ -219,7 +219,7 @@ static __poll_t rds_poll(struct file *file, struct socket *sock,
>
> poll_wait(file, sk_sleep(sk), wait);
>
> - if (rs->rs_seen_congestion)
> + if (READ_ONCE(rs->rs_seen_congestion))
> poll_wait(file, &rds_poll_waitq, wait);
>
> read_lock_irqsave(&rs->rs_recv_lock, flags);
> @@ -247,7 +247,7 @@ static __poll_t rds_poll(struct file *file, struct socket *sock,
>
> /* clear state any time we wake a seen-congested socket */
> if (mask)
> - rs->rs_seen_congestion = 0;
> + WRITE_ONCE(rs->rs_seen_congestion, 0);
>
> return mask;
> }
> diff --git a/net/rds/send.c b/net/rds/send.c
> index d8b14ff9d366..e5d58c29aabe 100644
> --- a/net/rds/send.c
> +++ b/net/rds/send.c
> @@ -1388,7 +1388,7 @@ int rds_sendmsg(struct socket *sock, struct msghdr *msg, size_t payload_len)
>
> ret = rds_cong_wait(conn->c_fcong, dport, nonblock, rs);
> if (ret) {
> - rs->rs_seen_congestion = 1;
> + WRITE_ONCE(rs->rs_seen_congestion, 1);
> goto out;
> }
> while (!rds_send_queue_rm(rs, conn, cpath, rm, rs->rs_bound_port,
prev parent reply other threads:[~2026-05-22 4:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 1:16 [PATCH net] rds: annotate data-race around rs_seen_congestion Jiayuan Chen
2026-05-22 4:49 ` Allison Henderson [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=ba093b6b93fffe07564e89dc5744efe45dfb4c21.camel@kernel.org \
--to=achender@kernel.org \
--cc=andy.grover@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiayuan.chen@linux.dev \
--cc=kuba@kernel.org \
--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=syzbot+fbf3648ae7f5bdb05c59@syzkaller.appspotmail.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