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, kuni1840@gmail.com,
netdev@vger.kernel.org
Subject: Re: [PATCH v1 net 0/2] af_unix: Fix inconsistent scc_index.
Date: Tue, 15 Sep 2026 23:50:06 +0000 [thread overview]
Message-ID: <178951620638.2322156.1829619954847633957.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260912030852.1467872-1-kuniyu@google.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 12 Sep 2026 03:07:50 +0000 you wrote:
> James Burton reported that a single SCC could have multiple
> scc_index and unix_vertex_dead() fails to detect a dead SCC.
>
> Patch 1 fixes it and Patch 2 adds a test case.
>
>
> Kuniyuki Iwashima (2):
> af_unix: Unify scc_index when finalising SCC in __unix_walk_scc().
> selftest: af_unix: Add test case with mixed lowpoint in scm_rights.c.
>
> [...]
Here is the summary with links:
- [v1,net,1/2] af_unix: Unify scc_index when finalising SCC in __unix_walk_scc().
https://git.kernel.org/netdev/net/c/4a4263dfeaba
- [v1,net,2/2] selftest: af_unix: Add test case with mixed lowpoint in scm_rights.c.
https://git.kernel.org/netdev/net/c/b645ccd41054
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-09-15 23:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 3:07 [PATCH v1 net 0/2] af_unix: Fix inconsistent scc_index Kuniyuki Iwashima
2026-09-12 3:07 ` [PATCH v1 net 1/2] af_unix: Unify scc_index when finalising SCC in __unix_walk_scc() Kuniyuki Iwashima
2026-09-12 3:07 ` [PATCH v1 net 2/2] selftest: af_unix: Add test case with mixed lowpoint in scm_rights.c Kuniyuki Iwashima
2026-09-15 7:27 ` [PATCH v1 net 0/2] af_unix: Fix inconsistent scc_index Simon Horman
2026-09-15 23:50 ` 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=178951620638.2322156.1829619954847633957.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=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 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.