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, eric.dumazet@gmail.com,
syzbot+f9f8efb58a4db2ca98d0@syzkaller.appspotmail.com
Subject: Re: [PATCH net-next] net: page_pool: fix general protection fault in page_pool_unlist
Date: Thu, 30 Nov 2023 18:20:26 +0000 [thread overview]
Message-ID: <170136842622.17358.1745471454100165762.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231130092259.3797753-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 30 Nov 2023 09:22:59 +0000 you wrote:
> syzbot was able to trigger a crash [1] in page_pool_unlist()
>
> page_pool_list() only inserts a page pool into a netdev page pool list
> if a netdev was set in params.
>
> Even if the kzalloc() call in page_pool_create happens to initialize
> pool->user.list, I chose to be more explicit in page_pool_list()
> adding one INIT_HLIST_NODE().
>
> [...]
Here is the summary with links:
- [net-next] net: page_pool: fix general protection fault in page_pool_unlist
https://git.kernel.org/netdev/net-next/c/f9893fdac319
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:[~2023-11-30 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 9:22 [PATCH net-next] net: page_pool: fix general protection fault in page_pool_unlist Eric Dumazet
2023-11-30 17:58 ` Andrew Lunn
2023-11-30 18:20 ` 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=170136842622.17358.1745471454100165762.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=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+f9f8efb58a4db2ca98d0@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 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).