From: Paolo Abeni <pabeni@redhat.com>
To: congei42@163.com, ecree.xilinx@gmail.com
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
kees@kernel.org, linux-net-drivers@amd.com,
linux-kernel@vger.kernel.org, netdev-bot+sashiko@kernel.org
Subject: Re: [PATCH net v2] sfc: fix use-after-free of filter_work in efx_realloc_channels()
Date: Thu, 29 Oct 2026 13:17:35 +0100 [thread overview]
Message-ID: <2172a7b5-a2ae-47b0-a28c-4df2eafca319@redhat.com> (raw)
In-Reply-To: <179310908138.3134.11515982039281965575@kernel.org>
On 10/27/26 14:51, netdev-bot+sashiko@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential
> issue(s) to consider.
>
> Critical: 0 · High: 0 (1) · Medium: 1 (1) · Low: 0
>
> If you believe none of the issues are legitimate, please reply to each
> issue of Medium severity or higher and explain why the AI is wrong.
> If any of them are legitimate and you plan to respin, please let patchwork
> know by including "pw-bot: cr" as a separate line at the end of your reply
> (one such reply per series is enough).
>
> - [Medium] After a ring resize, the replacement channel's aRFS expiry
> work is never started, so periodic expiry stops on that channel.
Looks legit.
@Edward: AFAICS sfc and siena use two different channel structs with
the same name and incompatible binary layout. That is quite evil...
/P
prev parent reply other threads:[~2026-10-29 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 13:42 [PATCH net v2] sfc: fix use-after-free of filter_work in efx_realloc_channels() Sicong Huang
2026-10-23 13:46 ` netdev-bot+sinfo
2026-10-27 13:51 ` netdev-bot+sashiko
2026-10-29 12:17 ` Paolo Abeni [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=2172a7b5-a2ae-47b0-a28c-4df2eafca319@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=congei42@163.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@kernel.org \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
/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