From: Jakub Kicinski <kuba@kernel.org>
To: Allison Henderson <allison.henderson@oracle.com>
Cc: "achender@kernel.org" <achender@kernel.org>,
"rds-devel@oss.oracle.com" <rds-devel@oss.oracle.com>,
"horms@kernel.org" <horms@kernel.org>,
"edumazet@google.com" <edumazet@google.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>
Subject: Re: [PATCH net-next v1 0/3] net/rds: RDS-TCP bug fix collection, subset 2: lock contention, state machine bugs, message drops
Date: Wed, 21 Jan 2026 17:39:20 -0800 [thread overview]
Message-ID: <20260121173920.71a093e5@kernel.org> (raw)
In-Reply-To: <83b05fbb38b2610b77d665850662a6f8c594f8cf.camel@oracle.com>
On Wed, 21 Jan 2026 17:50:19 +0000 Allison Henderson wrote:
> Sure, I will drop the "bug fixes" language and remove the Fixes tag
> from patch 2. Also, we noticed a potential race in patch 1, so I'm
> going to hold off on that patch for now. If that sounds good, I'll
> send v2 with those changes.
SG!
prev parent reply other threads:[~2026-01-22 1:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-18 2:49 [PATCH net-next v1 0/3] net/rds: RDS-TCP bug fix collection, subset 2: lock contention, state machine bugs, message drops Allison Henderson
2026-01-18 2:49 ` [PATCH net-next v1 1/3] net/rds: Change return code from rds_send_xmit() when lock is taken Allison Henderson
2026-01-18 2:49 ` [PATCH net-next v1 2/3] net/rds: No shortcut out of RDS_CONN_ERROR Allison Henderson
2026-01-18 2:49 ` [PATCH net-next v1 3/3] net/rds: rds_tcp_accept_one ought to not discard messages Allison Henderson
2026-01-21 3:09 ` [PATCH net-next v1 0/3] net/rds: RDS-TCP bug fix collection, subset 2: lock contention, state machine bugs, message drops Jakub Kicinski
2026-01-21 17:50 ` Allison Henderson
2026-01-22 1:39 ` 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=20260121173920.71a093e5@kernel.org \
--to=kuba@kernel.org \
--cc=achender@kernel.org \
--cc=allison.henderson@oracle.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox