From: patchwork-bot+netdevbpf@kernel•org
To: Yunsheng Lin <linyunsheng@huawei•com>
Cc: davem@davemloft•net, kuba@kernel•org, pabeni@redhat•com,
netdev@vger•kernel.org, linux-kernel@vger•kernel.org,
hawk@kernel•org, ilias.apalodimas@linaro•org,
edumazet@google•com, lorenzo@kernel•org, daniel@iogearbox•net,
john.fastabend@gmail•com
Subject: Re: [PATCH net] page_pool: fix inconsistency for page_pool_ring_[un]lock()
Date: Wed, 24 May 2023 03:40:19 +0000 [thread overview]
Message-ID: <168489961948.3716.18030218604369017925.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230522031714.5089-1-linyunsheng@huawei.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Mon, 22 May 2023 11:17:14 +0800 you wrote:
> page_pool_ring_[un]lock() use in_softirq() to decide which
> spin lock variant to use, and when they are called in the
> context with in_softirq() being false, spin_lock_bh() is
> called in page_pool_ring_lock() while spin_unlock() is
> called in page_pool_ring_unlock(), because spin_lock_bh()
> has disabled the softirq in page_pool_ring_lock(), which
> causes inconsistency for spin lock pair calling.
>
> [...]
Here is the summary with links:
- [net] page_pool: fix inconsistency for page_pool_ring_[un]lock()
https://git.kernel.org/netdev/net/c/368d3cb406cd
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:[~2023-05-24 3:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 3:17 [PATCH net] page_pool: fix inconsistency for page_pool_ring_[un]lock() Yunsheng Lin
2023-05-22 11:08 ` Jesper Dangaard Brouer
2023-05-22 11:45 ` Ilias Apalodimas
2023-05-23 2:13 ` Yunsheng Lin
2023-05-23 2:22 ` Jakub Kicinski
2023-05-23 2:34 ` Yunsheng Lin
2023-05-23 7:08 ` Jesper Dangaard Brouer
2023-05-23 8:16 ` Yunsheng Lin
2023-05-24 3:40 ` patchwork-bot+netdevbpf [this message]
2023-05-26 19:34 ` Jakub Kicinski
2023-05-27 7:56 ` Yunsheng Lin
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=168489961948.3716.18030218604369017925.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=hawk@kernel$(echo .)org \
--cc=ilias.apalodimas@linaro$(echo .)org \
--cc=john.fastabend@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linyunsheng@huawei$(echo .)com \
--cc=lorenzo@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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