From: Simon Horman <horms@kernel.org>
To: netdev-bot+sashiko@kernel.org
Cc: benquike@gmail.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: slip: fix out-of-bounds access on short CSLIP packets
Date: Tue, 22 Sep 2026 20:36:53 +0100 [thread overview]
Message-ID: <20260922193653.GH13925@horms.kernel.org> (raw)
In-Reply-To: <178994445036.2160803.93100448666025209@kernel.org>
On Sun, Sep 20, 2026 at 10:47:30PM +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 (1) · Low: 2 (1)
>
> 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] Commit message describes work that the patch does not do, and
> names the wrong bug class.
> - [Low] The new reserve literal 120 in sl_bump()
> (drivers/net/slip/slip.c:338) is undocumented and unlinked to the code…
> - [Low] The Fixes tag is wrong.
The concerns above seem legitimate.
>
> Pre-existing issues:
> - [Medium] The rx_over_errors early return in sl_bump()
> (drivers/net/slip/slip.c:338-341) discards a compressed frame without…
> - [Low] Claimed TOCTOU race between the reserve check in sl_bump() and
> sl_realloc_bufs() swapping/shrinking sl->rbuff and sl->buffsize.
I'm less convinced that the above are in-scope for this patch.
--
pw-bot: changes-requested
next prev parent reply other threads:[~2026-09-22 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 22:34 Hui Peng
2026-09-20 22:47 ` netdev-bot+sashiko
2026-09-22 19:36 ` Simon Horman [this message]
2026-09-21 15:11 ` krzk
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=20260922193653.GH13925@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=benquike@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®