All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: David Howells <dhowells@redhat.com>
Cc: netdev@vger.kernel.org, faith@zellic.io, pumpkin@devco.re,
	marc.dionne@auristor.com, niro@wiz.io, w@1wt.eu,
	edumazet@google.com, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org,
	linux-afs@lists.infradead.org, security@kernel.org,
	stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] rxrpc: Fix recvmsg() unconditional requeue
Date: Mon, 19 Jan 2026 18:10:08 +0000	[thread overview]
Message-ID: <176884620879.85277.2855458086448073147.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <95163.1768428203@warthog.procyon.org.uk>

Hello:

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

On Wed, 14 Jan 2026 22:03:23 +0000 you wrote:
> If rxrpc_recvmsg() fails because MSG_DONTWAIT was specified but the call at
> the front of the recvmsg queue already has its mutex locked, it requeues
> the call - whether or not the call is already queued.  The call may be on
> the queue because MSG_PEEK was also passed and so the call was not dequeued
> or because the I/O thread requeued it.
> 
> The unconditional requeue may then corrupt the recvmsg queue, leading to
> things like UAFs or refcount underruns.
> 
> [...]

Here is the summary with links:
  - [net,v2] rxrpc: Fix recvmsg() unconditional requeue
    https://git.kernel.org/netdev/net/c/2c28769a51de

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-01-19 18:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14 22:03 [PATCH net v2] rxrpc: Fix recvmsg() unconditional requeue David Howells
2026-01-19 15:10 ` Simon Horman
2026-01-19 18:05   ` Jakub Kicinski
2026-01-19 18:07 ` Jakub Kicinski
2026-01-19 18:10 ` 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=176884620879.85277.2855458086448073147.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=edumazet@google.com \
    --cc=faith@zellic.io \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.dionne@auristor.com \
    --cc=netdev@vger.kernel.org \
    --cc=niro@wiz.io \
    --cc=pabeni@redhat.com \
    --cc=pumpkin@devco.re \
    --cc=security@kernel.org \
    --cc=stable@kernel.org \
    --cc=w@1wt.eu \
    /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.