From: patchwork-bot+netdevbpf@kernel.org
To: Sunday Adelodun <adelodunolaoluwa@yahoo.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
kuniyu@google.com, skhan@linuxfoundation.org,
david.hunter.linux@gmail.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH v6] selftests: af_unix: Add tests for ECONNRESET and EOF semantics
Date: Tue, 18 Nov 2025 10:40:06 +0000 [thread overview]
Message-ID: <176346240626.4087956.15974083962638207959.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251113112802.44657-1-adelodunolaoluwa@yahoo.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 13 Nov 2025 12:28:02 +0100 you wrote:
> Add selftests to verify and document Linux’s intended behaviour for
> UNIX domain sockets (SOCK_STREAM and SOCK_DGRAM) when a peer closes.
> The tests verify that:
>
> 1. SOCK_STREAM returns EOF when the peer closes normally.
> 2. SOCK_STREAM returns ECONNRESET if the peer closes with unread data.
> 3. SOCK_SEQPACKET returns EOF when the peer closes normally.
> 4. SOCK_SEQPACKET returns ECONNRESET if the peer closes with unread data.
> 5. SOCK_DGRAM does not return ECONNRESET when the peer closes.
>
> [...]
Here is the summary with links:
- [v6] selftests: af_unix: Add tests for ECONNRESET and EOF semantics
https://git.kernel.org/netdev/net-next/c/45a1cd8346ca
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-11-18 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251113112802.44657-1-adelodunolaoluwa.ref@yahoo.com>
2025-11-13 11:28 ` [PATCH v6] selftests: af_unix: Add tests for ECONNRESET and EOF semantics Sunday Adelodun
2025-11-18 10:40 ` 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=176346240626.4087956.15974083962638207959.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=adelodunolaoluwa@yahoo.com \
--cc=davem@davemloft.net \
--cc=david.hunter.linux@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox