public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Kuniyuki Iwashima <kuniyu@google•com>
Cc: davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
	pabeni@redhat•com, horms@kernel•org, kuni1840@gmail•com,
	torvalds@linuxfoundation•org, netdev@vger•kernel.org,
	sysroot314@gmail•com
Subject: Re: [PATCH v3 net] af_unix: Give up GC if MSG_PEEK intervened.
Date: Thu, 12 Mar 2026 20:40:05 +0000	[thread overview]
Message-ID: <177334800580.549113.8658019831602946307.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260311054043.1231316-1-kuniyu@google.com>

Hello:

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

On Wed, 11 Mar 2026 05:40:40 +0000 you wrote:
> Igor Ushakov reported that GC purged the receive queue of
> an alive socket due to a race with MSG_PEEK with a nice repro.
> 
> This is the exact same issue previously fixed by commit
> cbcf01128d0a ("af_unix: fix garbage collect vs MSG_PEEK").
> 
> After GC was replaced with the current algorithm, the cited
> commit removed the locking dance in unix_peek_fds() and
> reintroduced the same issue.
> 
> [...]

Here is the summary with links:
  - [v3,net] af_unix: Give up GC if MSG_PEEK intervened.
    https://git.kernel.org/netdev/net/c/e5b31d988a41

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



  reply	other threads:[~2026-03-12 20:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11  5:40 [PATCH v3 net] af_unix: Give up GC if MSG_PEEK intervened Kuniyuki Iwashima
2026-03-12 20:40 ` patchwork-bot+netdevbpf [this message]
2026-04-07 15:58 ` Lee Jones
2026-04-07 16:03   ` Kuniyuki Iwashima
2026-04-07 17:01   ` Greg KH

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=177334800580.549113.8658019831602946307.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=horms@kernel$(echo .)org \
    --cc=kuba@kernel$(echo .)org \
    --cc=kuni1840@gmail$(echo .)com \
    --cc=kuniyu@google$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=sysroot314@gmail$(echo .)com \
    --cc=torvalds@linuxfoundation$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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