From: Jakub Kicinski <kuba@kernel.org>
To: Bryam Vargas via B4 Relay <devnull+hexlabsecurity.proton.me@kernel.org>
Cc: hexlabsecurity@proton.me, "D. Wythe" <alibuda@linux.alibaba.com>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Mahanta Jambigi <mjambigi@linux.ibm.com>,
Dust Li <dust.li@linux.alibaba.com>,
Wen Gu <guwen@linux.alibaba.com>,
"David S. Miller" <davem@davemloft.net>,
Sidraya Jayagond <sidraya@linux.ibm.com>,
Wenjia Zhang <wenjia@linux.ibm.com>,
Tony Lu <tonylu@linux.alibaba.com>,
netdev@vger.kernel.org, Simon Horman <horms@kernel.org>,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3] net/smc: order the CDC receive path against buffer publication
Date: Thu, 23 Jul 2026 07:31:53 -0700 [thread overview]
Message-ID: <20260723073153.1b7fabd9@kernel.org> (raw)
In-Reply-To: <20260716-b4-disp-aa52955a-v3-1-03a4411a7549@proton.me>
On Thu, 16 Jul 2026 08:50:45 -0500 Bryam Vargas via B4 Relay wrote:
> No Fixes: tag -- the rmb_desc ordering is foundational (predates the git history
> here); the sndbuf_desc hunks additionally cover the later SMC-D DMB-nocopy path.
> Happy to split rmb/sndbuf for a cleaner stable backport.
:/ Fixes tag should point to the first commit adding the code if it
"has always been there".
--
pw-bot: cr
prev parent reply other threads:[~2026-07-23 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 13:50 [PATCH net v3] net/smc: order the CDC receive path against buffer publication Bryam Vargas via B4 Relay
2026-07-16 13:50 ` Bryam Vargas
2026-07-17 13:50 ` sashiko-bot
2026-07-23 14:31 ` 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=20260723073153.1b7fabd9@kernel.org \
--to=kuba@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=devnull+hexlabsecurity.proton.me@kernel.org \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=hexlabsecurity@proton.me \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjambigi@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sidraya@linux.ibm.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.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.