All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Bryam Vargas <hexlabsecurity@proton.me>
Cc: dust.li@linux.alibaba.com, sidraya@linux.ibm.com,
	pabeni@redhat.com, davem@davemloft.net, kuba@kernel.org,
	wenjia@linux.ibm.com, alibuda@linux.alibaba.com,
	mjambigi@linux.ibm.com, tonylu@linux.alibaba.com,
	guwen@linux.alibaba.com, edumazet@google.com,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	netdev@vger.kernel.org, horms@kernel.org,
	linux-s390@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] net/smc: close the SMC-D teardown window around the ghost send buffer
Date: Fri, 14 Aug 2026 03:23:51 +0000	[thread overview]
Message-ID: <178667783138.3150297.14142348032693681009.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260808-b4-disp-22f119e6-v2-0-61647601a6f3@proton.me>

Hello:

This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sat, 08 Aug 2026 02:21:22 -0500 you wrote:
> Both patches only matter on the SMC-D DMB-nocopy path, where the ghost send
> buffer exists, and the only in-tree provider of support_mmapped_rdmb is
> dibs_loopback. CONFIG_DIBS_LO is default n and its help calls it a testing aid,
> so on a stock config neither bug is reachable.
> 
> v1 moved smcd_buf_detach() after the drain. Dust Li replied that it does not
> fully eliminate the race and asked whether RCU is the better shape. He is right
> about the first part; I built both and measured them.
> 
> [...]

Here is the summary with links:
  - [net,v2,1/2] net/smc: unregister the connection before draining the rx tasklet
    https://git.kernel.org/netdev/net/c/36cdf5d48ca1
  - [net,v2,2/2] net/smc: do not dereference an unset send buffer on the SMC-D teardown path
    https://git.kernel.org/netdev/net/c/b395dd319cea

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-08-14  3:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-08  7:21 [PATCH net v2 0/2] net/smc: close the SMC-D teardown window around the ghost send buffer Bryam Vargas via B4 Relay
2026-08-08  7:21 ` Bryam Vargas
2026-08-08  7:21 ` [PATCH net v2 1/2] net/smc: unregister the connection before draining the rx tasklet Bryam Vargas via B4 Relay
2026-08-08  7:21   ` Bryam Vargas
2026-08-09  7:21   ` sashiko-bot
2026-08-13  5:47   ` Sidraya Jayagond
2026-08-13  7:29   ` Tony Lu
2026-08-08  7:21 ` [PATCH net v2 2/2] net/smc: do not dereference an unset send buffer on the SMC-D teardown path Bryam Vargas via B4 Relay
2026-08-08  7:21   ` Bryam Vargas
2026-08-09  7:21   ` sashiko-bot
2026-08-13  5:47   ` Sidraya Jayagond
2026-08-13  7:29   ` Tony Lu
2026-08-13  0:10 ` [PATCH net v2 0/2] net/smc: close the SMC-D teardown window around the ghost send buffer Jakub Kicinski
2026-08-14  3:23 ` patchwork-bot+netdevbpf [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=178667783138.3150297.14142348032693681009.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alibuda@linux.alibaba.com \
    --cc=davem@davemloft.net \
    --cc=dust.li@linux.alibaba.com \
    --cc=edumazet@google.com \
    --cc=guwen@linux.alibaba.com \
    --cc=hexlabsecurity@proton.me \
    --cc=horms@kernel.org \
    --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 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.