From: patchwork-bot+netdevbpf@kernel.org
To: John Daley <johndale@cisco.com>
Cc: shuah@kernel.org, kuba@kernel.org, sdf@fomichev.me,
willemb@google.com, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/1] selftests: drv-net-hw: fix pp_alloc_fail test error
Date: Fri, 17 Jan 2025 01:20:32 +0000 [thread overview]
Message-ID: <173707683202.1645866.2260732014925213405.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250115181312.3544-1-johndale@cisco.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 15 Jan 2025 10:13:11 -0800 you wrote:
> The tool pp_alloc_fail.py tested error recovery by injecting errors
> into page_pool_alloc_pages(). Perhaps due to the netmems conversion,
> page_pool_put_full_page() does not end up calling that function.
>
> page_pool_alloc_netmems() seems to be the base function for all the
> the allocation functions in the API call, so put the error injection
> there instead.
>
> [...]
Here is the summary with links:
- [net-next,1/1] selftests: drv-net-hw: inject pp_alloc_fail errors in the right place
https://git.kernel.org/netdev/net-next/c/8d20dcda404d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-01-17 1:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 18:13 [PATCH net-next 0/1] selftests: drv-net-hw: fix pp_alloc_fail test error John Daley
2025-01-15 18:13 ` [PATCH net-next 1/1] selftests: drv-net-hw: inject pp_alloc_fail errors in the right place John Daley
2025-01-17 1:20 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-14 22:31 [PATCH net-next 0/1] selftests: drv-net-hw: fix pp_alloc_fail test error John Daley
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=173707683202.1645866.2260732014925213405.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=johndale@cisco.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=willemb@google.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