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, aconole@bytheb.org,
kuni1840@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH v1 net 0/2] af_unix: Fix SO_PEEK_OFF bug in unix_stream_read_generic().
Date: Wed, 19 Nov 2025 03:30:09 +0000 [thread overview]
Message-ID: <176352300975.209489.12309467398013047614.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251117174740.3684604-1-kuniyu@google.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 17 Nov 2025 17:47:09 +0000 you wrote:
> Miao Wang reported a bug of SO_PEEK_OFF on AF_UNIX SOCK_STREAM socket.
>
> Patch 1 fixes the bug and Patch 2 adds a new selftest to cover the case.
>
>
> Kuniyuki Iwashima (2):
> af_unix: Read sk_peek_offset() again after sleeping in
> unix_stream_read_generic().
> selftest: af_unix: Add test for SO_PEEK_OFF.
>
> [...]
Here is the summary with links:
- [v1,net,1/2] af_unix: Read sk_peek_offset() again after sleeping in unix_stream_read_generic().
https://git.kernel.org/netdev/net/c/7bf3a476ce43
- [v1,net,2/2] selftest: af_unix: Add test for SO_PEEK_OFF.
https://git.kernel.org/netdev/net/c/e1bb28bf13f4
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-19 3:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 17:47 [PATCH v1 net 0/2] af_unix: Fix SO_PEEK_OFF bug in unix_stream_read_generic() Kuniyuki Iwashima
2025-11-17 17:47 ` [PATCH v1 net 1/2] af_unix: Read sk_peek_offset() again after sleeping " Kuniyuki Iwashima
2025-11-17 17:47 ` [PATCH v1 net 2/2] selftest: af_unix: Add test for SO_PEEK_OFF Kuniyuki Iwashima
2025-11-17 23:09 ` Miao Wang
2025-11-18 4:10 ` Kuniyuki Iwashima
2025-11-18 1:26 ` Jakub Kicinski
2025-11-18 3:07 ` Kuniyuki Iwashima
2025-11-19 3: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=176352300975.209489.12309467398013047614.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aconole@bytheb.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).