Netdev List
 help / color / mirror / Atom feed
From: netdev-bot+sashiko@kernel.org
To: achender@kernel.org
Cc: netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	pabeni@redhat.com, edumazet@google.com, kuba@kernel.org,
	horms@kernel.org
Subject: Re: [PATCH net-next v9 11/13] net/rds: hold connection references in lookup, sockets and c_passive
Date: Mon, 12 Oct 2026 04:17:48 +0000	[thread overview]
Message-ID: <179177866895.434549.7210189401396244719@kernel.org> (raw)
In-Reply-To: <20261008031333.1142174-12-achender@kernel.org>

Thank you for your contribution! Sashiko AI review found more severe
issue(s) in other patches of this series. This mail is only an FYI, in case
you want to address the nit picks below when you respin.

Low priority / nit picks for your consideration:

- [Low] The commit's attribution trailers contradict each other.

--

net/rds: hold connection references in lookup, sockets and c_passive

This patch makes struct rds_connection pointers carry real references in
rds_conn_lookup(), __rds_conn_create(), the rs->rs_conn sendmsg cache and
parent->c_passive. It also serializes the rs_conn cache and the ToS
ioctls under rs_lock, which closes a syzbot-reported KCSAN data race
between concurrent rds_sendmsg() calls on the same socket.

Closes: https://syzkaller.appspot.com/bug?extid=879c1877016972360186

> Reported-by: syzbot+879c1877016972360186@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=879c1877016972360186
> Signed-off-by: Sharath Srinivasan <sharath.srinivasan@oracle.com>
> [achender: substantial reimplementation for net-next: upstream has no
>  conn reaper, per-conn workers hold no references (destroy cancels
>  them synchronously before the final put), and the sendmsg cache is
>  serialized with rs_lock instead of UEK's socket flag; rewrite commit
>  message]
> Assisted-by: Claude-Code:claude-fable-5
> Signed-off-by: Allison Henderson <achender@kernel.org>

[Severity: Low]
This isn't a bug, but do the attribution trailers match each other?

The From: author is Allison Henderson. The first Signed-off-by is
Sharath Srinivasan's, though, and there is no Co-developed-by: tag for
him.

Documentation/process/submitting-patches.rst says the first SoB entry
signals primary authorship. It also says each Co-developed-by: must be
immediately followed by that co-author's SoB.

The "[achender: ...]" bracket note is the convention a handler uses when
editing someone else's patch. Because of it, the chain reads as Sharath's
patch carried by Allison.

The message also calls this a "substantial reimplementation" that is only
"Based on the Oracle UEK commits". That suggests Sharath's bare SoB
certifies code he did not write in this form.

Would it be better to pick one of these two layouts?

  - Make Sharath the author and keep the bracket note.

  - Keep Allison as the author, add "Co-developed-by: Sharath Srinivasan"
    immediately before his Signed-off-by, and drop the bracket note.

For comparison, "net/rds: split connection destroy into quiesce and
kref-governed free" and "net/rds: wait for connections to be freed on
transport unload" in the same series are authored by Sharath. They use
this same trailer layout, and there it is consistent.

-- 
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261008031333.1142174-1-achender%40kernel.org

  reply	other threads:[~2026-10-12  4:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08  3:13 [PATCH net-next v9 00/13] net/rds: make connection lifetime reference-counted Allison Henderson
2026-10-08  3:13 ` [PATCH net-next v9 01/13] net/rds: ib: don't enable interrupts in rds_ib_conn_free() Allison Henderson
2026-10-08  3:13 ` [PATCH net-next v9 02/13] net/rds: undo conn_alloc() the same way on every __rds_conn_create() exit Allison Henderson
2026-10-08  3:13 ` [PATCH net-next v9 03/13] net/rds: ib: refuse to attach a connection to a device being removed Allison Henderson
2026-10-12  4:17   ` netdev-bot+sashiko
2026-10-08  3:13 ` [PATCH net-next v9 04/13] net/rds: guard every work-requeueing site with rds_destroy_pending() Allison Henderson
2026-10-08  3:13 ` [PATCH net-next v9 05/13] net/rds: make rds_destroy_pending() report a connection's own destroy Allison Henderson
2026-10-08  3:13 ` [PATCH net-next v9 06/13] net/rds: split connection destroy into quiesce and kref-governed free Allison Henderson
2026-10-08  3:13 ` [PATCH net-next v9 07/13] net/rds: unlink transport nodes before a possibly deferred connection free Allison Henderson
2026-10-12  4:17   ` netdev-bot+sashiko
2026-10-08  3:13 ` [PATCH net-next v9 08/13] net/rds: wait for connections to be freed on transport unload Allison Henderson
2026-10-08  3:13 ` [PATCH net-next v9 09/13] net/rds: hold a connection reference from struct rds_incoming Allison Henderson
2026-10-12  4:17   ` netdev-bot+sashiko
2026-10-08  3:13 ` [PATCH net-next v9 10/13] net/rds: take cp_lock to purge cp_send_queue in the quiesce Allison Henderson
2026-10-08  3:13 ` [PATCH net-next v9 11/13] net/rds: hold connection references in lookup, sockets and c_passive Allison Henderson
2026-10-12  4:17   ` netdev-bot+sashiko [this message]
2026-10-08  3:13 ` [PATCH net-next v9 12/13] net/rds: pin the connection across RDMA-CM event handling Allison Henderson
2026-10-08  3:13 ` [PATCH net-next v9 13/13] net/rds: drop rds_conn_count in favor of t_conn_count Allison Henderson

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=179177866895.434549.7210189401396244719@kernel.org \
    --to=netdev-bot+sashiko@kernel.org \
    --cc=achender@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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