From: Simon Horman <horms@kernel.org>
To: netdev-bot+sashiko@kernel.org
Cc: victor@mojatatu.com, netdev@vger.kernel.org, jiri@resnulli.us,
jhs@mojatatu.com, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, sashiko-bot@kernel.org
Subject: Re: [PATCH net-next v2] net/sched: em_text: pad the text pattern in the ematch dump
Date: Thu, 19 Nov 2026 13:37:20 +0000 [thread overview]
Message-ID: <20261119133720.GY860048@horms.kernel.org> (raw)
In-Reply-To: <179494556684.3136.3254895311432959761@kernel.org>
On Tue, Nov 17, 2026 at 07:59:26PM +0000, netdev-bot+sashiko@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 3 potential
> issue(s) to consider.
>
> Critical: 0 · High: 0 · Medium: 1 · Low: 2
>
> 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] The commit message says "A padded text ematch is the same size
> as the request that installed it ... Since the dump is no larger than…
> - [Low] The patch fixes a long-standing, user-visible netlink dump bug
> but carries no Fixes: tag.
> - [Low] The commit message describes the impact as "the ematch list is
> therefore misparsed", and its reproducer needs two text ematches.
Hi Victor and Jamal,
I'd appreciate if you could respond to Sashiko.
Even if it is only for the record.
Thanks!
next prev parent reply other threads:[~2026-11-19 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 19:10 [PATCH net-next v2] net/sched: em_text: pad the text pattern in the ematch dump Victor Nogueira
2026-11-17 19:59 ` netdev-bot+sashiko
2026-11-19 13:37 ` Simon Horman [this message]
2026-11-17 22:16 ` Stephen Hemminger
2026-11-17 22:54 ` Jamal Hadi Salim
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=20261119133720.GY860048@horms.kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sashiko-bot@kernel.org \
--cc=victor@mojatatu.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