From: patchwork-bot+netdevbpf@kernel.org
To: Jhonata Poma-Hansen <jhonata.poma@gmail.com>
Cc: davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, kuniyu@google.com,
m.szyprowski@samsung.com
Subject: Re: [PATCH net v2 0/2] netlink: fix a dump livelock with a notification queued
Date: Thu, 29 Oct 2026 16:30:14 +0000 [thread overview]
Message-ID: <179329141429.559085.11181386542517865793.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261027-netlink-dump-livelock-v2-0-c4bb05352a33@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 27 Oct 2026 15:04:00 +0100 you wrote:
> A netlink dump that starts while a notification is still charged to a
> socket with a small receive buffer fails with ENOBUFS, and every retry
> from recvmsg() fails the same way. A reader that peeks before reading,
> as libnl does, never consumes the message at the head of the queue and
> spins forever. I hit this with "iw dev wlan0 scan" on an arm64 board.
>
> Patch 1 goes back to checking sk_rcvbuf before charging the dump skb,
> as before commit ae8f160e7eb2. Patch 2 adds a selftest; it fails
> without patch 1 and is skipped without the privileges to create a
> netns.
>
> [...]
Here is the summary with links:
- [net,v2,1/2] netlink: check sk_rcvbuf before charging the dump skb
https://git.kernel.org/netdev/net/c/b45d37740cfb
- [net,v2,2/2] selftests: net: netlink-dumps: start a dump with a notification queued
https://git.kernel.org/netdev/net/c/e615d0a8b201
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-10-29 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 14:04 [PATCH net v2 0/2] netlink: fix a dump livelock with a notification queued Jhonata Poma-Hansen via B4 Relay
2026-10-27 14:04 ` [PATCH net v2 1/2] netlink: check sk_rcvbuf before charging the dump skb Jhonata Poma-Hansen via B4 Relay
2026-10-27 16:17 ` Eric Dumazet
2026-10-27 14:04 ` [PATCH net v2 2/2] selftests: net: netlink-dumps: start a dump with a notification queued Jhonata Poma-Hansen via B4 Relay
2026-10-29 16: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=179329141429.559085.11181386542517865793.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=jhonata.poma@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.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