From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, horms@kernel.org, eric.dumazet@gmail.com,
syzbot+f56a5c5eac2b28439810@syzkaller.appspotmail.com,
jasowang@redhat.com, mst@redhat.com
Subject: Re: [PATCH net-next] ptr_ring: do not block hard interrupts in ptr_ring_resize_multiple()
Date: Thu, 19 Dec 2024 02:10:31 +0000 [thread overview]
Message-ID: <173457423152.1793000.3704693558599997628.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241217135121.326370-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 17 Dec 2024 13:51:21 +0000 you wrote:
> Jakub added a lockdep_assert_no_hardirq() check in __page_pool_put_page()
> to increase test coverage.
>
> syzbot found a splat caused by hard irq blocking in
> ptr_ring_resize_multiple() [1]
>
> As current users of ptr_ring_resize_multiple() do not require
> hard irqs being masked, replace it to only block BH.
>
> [...]
Here is the summary with links:
- [net-next] ptr_ring: do not block hard interrupts in ptr_ring_resize_multiple()
https://git.kernel.org/netdev/net-next/c/a126061c80d5
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:[~2024-12-19 2:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 13:51 [PATCH net-next] ptr_ring: do not block hard interrupts in ptr_ring_resize_multiple() Eric Dumazet
2024-12-17 14:41 ` Michael S. Tsirkin
2024-12-18 2:41 ` Jason Wang
2024-12-19 2:10 ` 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=173457423152.1793000.3704693558599997628.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+f56a5c5eac2b28439810@syzkaller.appspotmail.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.