From: Alexandra Winter <wintera@linux.ibm.com>
To: hexlabsecurity@proton.me,
Mahanta Jambigi <mjambigi@linux.ibm.com>,
"D. Wythe" <alibuda@linux.alibaba.com>,
"David S. Miller" <davem@davemloft.net>,
Dust Li <dust.li@linux.alibaba.com>,
Jakub Kicinski <kuba@kernel.org>,
Sidraya Jayagond <sidraya@linux.ibm.com>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Hidayath Khan <hidayath@linux.ibm.com>,
Julian Ruess <julianr@linux.ibm.com>,
Wenjia Zhang <wenjia@linux.ibm.com>,
linux-rdma@vger.kernel.org, Wen Gu <guwen@linux.alibaba.com>,
Tony Lu <tonylu@linux.alibaba.com>,
netdev@vger.kernel.org, Simon Horman <horms@kernel.org>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH net 0/2] net/smc: do not reuse the DMB of a nocopy device
Date: Mon, 16 Nov 2026 16:27:51 +0100 [thread overview]
Message-ID: <f23d9c47-b254-484f-b0c4-d1053d337c64@linux.ibm.com> (raw)
In-Reply-To: <20261113-b4-disp-19244662-v1-0-39b256b70ca7@proton.me>
On 13.11.26 14:57, Bryam Vargas via B4 Relay wrote:
[...]
>
> ISM pools its DMBs the same way and an old ISM peer also writes its CDCs
> by token, so AFAICT the reuse applies there too. This series does not
> change ISM, and I have not tested it.
ISM does not provide an attach operation. So nobody will write into a
receive buffer dmb after dmb_unregister.
prev parent reply other threads:[~2026-11-16 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 13:57 [PATCH net 0/2] net/smc: do not reuse the DMB of a nocopy device Bryam Vargas via B4 Relay
2026-11-13 13:57 ` [PATCH net 1/2] dibs: loopback: reset the client id when the owner unregisters a DMB Bryam Vargas via B4 Relay
2026-11-13 13:57 ` [PATCH net 2/2] net/smc: do not reuse the DMB of a nocopy device Bryam Vargas via B4 Relay
2026-11-16 15:27 ` Alexandra Winter [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=f23d9c47-b254-484f-b0c4-d1053d337c64@linux.ibm.com \
--to=wintera@linux.ibm.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@kernel.org \
--cc=guwen@linux.alibaba.com \
--cc=hexlabsecurity@proton.me \
--cc=hidayath@linux.ibm.com \
--cc=horms@kernel.org \
--cc=julianr@linux.ibm.com \
--cc=kuba@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox