All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Mahanta Jambigi <mjambigi@linux.ibm.com>,
	Alexandra Winter <wintera@linux.ibm.com>,
	"D. Wythe" <alibuda@linux.alibaba.com>
Cc: Bryam Vargas via B4 Relay
	<devnull+hexlabsecurity.proton.me@kernel.org>,
	hexlabsecurity@proton.me, Dust Li <dust.li@linux.alibaba.com>,
	"David S. Miller" <davem@davemloft.net>,
	Paolo Abeni <pabeni@redhat.com>,
	Eric Dumazet <edumazet@kernel.org>,
	Sidraya Jayagond <sidraya@linux.ibm.com>,
	Hidayath Khan <hidayath@linux.ibm.com>,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	netdev@vger.kernel.org, Simon Horman <horms@kernel.org>,
	Tony Lu <tonylu@linux.alibaba.com>,
	Wen Gu <guwen@linux.alibaba.com>,
	linux-s390@vger.kernel.org, Wenjia Zhang <wenjia@linux.ibm.com>,
	Julian Ruess <julianr@linux.ibm.com>
Subject: Re: [PATCH net v2 0/2] net/smc: do not reuse the DMB of a nocopy device
Date: Wed, 18 Nov 2026 16:24:08 -0800	[thread overview]
Message-ID: <20261118162408.215ca3d1@kernel.org> (raw)
In-Reply-To: <20261114-b4-disp-4e6374c2-v2-0-3b7050bddef7@proton.me>

On Sat, 14 Nov 2026 14:09:27 -0500 Bryam Vargas via B4 Relay wrote:
> With DMB nocopy (the dibs loopback device) a peer writes into the other
> end's RMB through its own attachment. smc_buf_unuse() puts that DMB back
> in the link group's pool with its token still registered, IOW the old
> peer can still send its CDCs to it. The next connection that takes the
> DMB gets those CDCs, and a peer that attaches after the other end gave
> up lands in another connection's DMB. 2/2 stops pooling DMBs on nocopy
> devices. This is the reused-DMB case that the v6 cover of the CDC
> receive ordering series [1] lists as not fixed; Sashiko flagged it on
> v5 2/2 [2].

SNC, DIBS maintainers, could you review this slop?

  parent reply	other threads:[~2026-11-19  0:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-14 19:09 [PATCH net v2 0/2] net/smc: do not reuse the DMB of a nocopy device Bryam Vargas
2026-11-14 19:09 ` Bryam Vargas via B4 Relay
2026-11-14 19:09 ` [PATCH net v2 1/2] dibs: loopback: reset the client id when the owner unregisters a DMB Bryam Vargas
2026-11-14 19:09   ` Bryam Vargas via B4 Relay
2026-11-15 19:09   ` sashiko-bot
2026-11-19  9:05   ` Alexandra Winter
2026-11-14 19:09 ` [PATCH net v2 2/2] net/smc: do not reuse the DMB of a nocopy device Bryam Vargas
2026-11-14 19:09   ` Bryam Vargas via B4 Relay
2026-11-15 19:09   ` sashiko-bot
2026-11-19  6:55   ` Sidraya Jayagond
2026-11-19  0:24 ` Jakub Kicinski [this message]
2026-11-19  9:06 ` [PATCH net v2 0/2] " Alexandra Winter

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=20261118162408.215ca3d1@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@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=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 \
    --cc=wintera@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.