From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, edumazet@google.com, vray@kalrayinc.com
Subject: Re: [PATCH v3 net] net: sched: fixed barrier to prevent skbuff sticking in qdisc backlog
Date: Fri, 27 May 2022 04:48:33 +0000 [thread overview]
Message-ID: <165362691353.5864.10388871011458588553.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220526001746.2437669-1-eric.dumazet@gmail.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 25 May 2022 17:17:46 -0700 you wrote:
> From: Vincent Ray <vray@kalrayinc.com>
>
> In qdisc_run_begin(), smp_mb__before_atomic() used before test_bit()
> does not provide any ordering guarantee as test_bit() is not an atomic
> operation. This, added to the fact that the spin_trylock() call at
> the beginning of qdisc_run_begin() does not guarantee acquire
> semantics if it does not grab the lock, makes it possible for the
> following statement :
>
> [...]
Here is the summary with links:
- [v3,net] net: sched: fixed barrier to prevent skbuff sticking in qdisc backlog
https://git.kernel.org/bpf/bpf/c/a54ce3703613
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:[~2022-05-27 4:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 0:17 [PATCH v3 net] net: sched: fixed barrier to prevent skbuff sticking in qdisc backlog Eric Dumazet
2022-05-27 4:48 ` 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=165362691353.5864.10388871011458588553.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=vray@kalrayinc.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.