From: patchwork-bot+netdevbpf@kernel.org
To: Soichiro Ueda <the.latticeheart@gmail.com>
Cc: kuniyu@google.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, netdev@vger.kernel.org, horms@kernel.org,
willemdebruijn.kernel@gmail.com, shuah@kernel.org,
shankerwangmiao@gmail.com, willemb@google.com
Subject: Re: [PATCH net-next v3] selftests: af_unix: validate SO_PEEK_OFF advancement and reset
Date: Thu, 12 Mar 2026 01:30:05 +0000 [thread overview]
Message-ID: <177327900555.3897363.9493224320335469172.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260310072832.127848-1-the.latticeheart@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 10 Mar 2026 16:28:31 +0900 you wrote:
> Extend the so_peek_off selftest to ensure the socket peek offset is handled
> correctly after both MSG_PEEK and actual data consumption.
>
> Verify that the peek offset advances by the same amount as the number of
> bytes read when performing a read with MSG_PEEK.
>
> After exercising SO_PEEK_OFF via MSG_PEEK, drain the receive queue with a
> non-peek recv() and verify that it can receive all the content in the
> buffer and SO_PEEK_OFF returns back to 0.
>
> [...]
Here is the summary with links:
- [net-next,v3] selftests: af_unix: validate SO_PEEK_OFF advancement and reset
https://git.kernel.org/netdev/net-next/c/34c0378b156f
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:[~2026-03-12 1:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 7:28 [PATCH net-next v3] selftests: af_unix: validate SO_PEEK_OFF advancement and reset Soichiro Ueda
2026-03-12 1:30 ` 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=177327900555.3897363.9493224320335469172.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=shankerwangmiao@gmail.com \
--cc=shuah@kernel.org \
--cc=the.latticeheart@gmail.com \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox