From: patchwork-bot+netdevbpf@kernel.org
To: Nikita Yushchenko <nikita.yoush@cogentembedded.com>
Cc: yoshihiro.shimoda.uh@renesas.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, geert+renesas@glider.be,
netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org, michael.dege@renesas.com,
christian.mardmoeller@renesas.com, dennis.ostermann@renesas.com
Subject: Re: [PATCH net] net: renesas: rswitch: rework ts tags management
Date: Sun, 15 Dec 2024 23:10:30 +0000 [thread overview]
Message-ID: <173430423099.3600507.2957319591923005123.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241212062558.436455-1-nikita.yoush@cogentembedded.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 12 Dec 2024 11:25:58 +0500 you wrote:
> The existing linked list based implementation of how ts tags are
> assigned and managed is unsafe against concurrency and corner cases:
> - element addition in tx processing can race against element removal
> in ts queue completion,
> - element removal in ts queue completion can race against element
> removal in device close,
> - if a large number of frames gets added to tx queue without ts queue
> completions in between, elements with duplicate tag values can get
> added.
>
> [...]
Here is the summary with links:
- [net] net: renesas: rswitch: rework ts tags management
https://git.kernel.org/netdev/net/c/922b4b955a03
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:[~2024-12-15 23:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 6:25 [PATCH net] net: renesas: rswitch: rework ts tags management Nikita Yushchenko
2024-12-15 23:10 ` patchwork-bot+netdevbpf [this message]
2024-12-16 11:25 ` Yoshihiro Shimoda
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=173430423099.3600507.2957319591923005123.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=christian.mardmoeller@renesas.com \
--cc=davem@davemloft.net \
--cc=dennis.ostermann@renesas.com \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=michael.dege@renesas.com \
--cc=netdev@vger.kernel.org \
--cc=nikita.yoush@cogentembedded.com \
--cc=pabeni@redhat.com \
--cc=yoshihiro.shimoda.uh@renesas.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