All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Steve Grubb <sgrubb@redhat.com>
Cc: netdev@vger.kernel.org, edumazet@google.com, kuniyu@google.com,
	pabeni@redhat.com, willemb@google.com, davem@davemloft.net,
	kuba@kernel.org, horms@kernel.org, shuah@kernel.org
Subject: Re: [PATCH net 1/1] net: preserve socketpair output on setup failure
Date: Thu, 17 Sep 2026 02:10:06 +0000	[thread overview]
Message-ID: <178961100687.3376729.11290258509445826746.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <JyK226D0S5CWGUpAC4MO4A@redhat.com>

Hello:

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

On Thu, 10 Sep 2026 13:53:15 -0400 you wrote:
> socketpair() writes the reserved descriptor numbers to userspace before
> creating the sockets and their file objects. A later failure therefore
> leaves a modified caller's array despite returning an error, contrary to
> POSIX. For example, socketpair(AF_UNIX, SOCK_STREAM, -1, fd) returns
> EPROTONOSUPPORT but replaces the array's sentinel values with unused fd
> numbers.
> 
> [...]

Here is the summary with links:
  - [net,1/1] net: preserve socketpair output on setup failure
    https://git.kernel.org/netdev/net-next/c/65734bbe4a9f

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-09-17  2:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10 17:53 [PATCH net 1/1] net: preserve socketpair output on setup failure Steve Grubb
2026-09-11 17:54 ` netdev-bot+sashiko
2026-09-17  2: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=178961100687.3376729.11290258509445826746.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sgrubb@redhat.com \
    --cc=shuah@kernel.org \
    --cc=willemb@google.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.