Netdev List
 help / color / mirror / Atom feed
From: phx <phx0fer@gmail.com>
To: netdev-bot+sinfo@kernel.org
Cc: vinicius.gomes@intel.com, jhs@mojatatu.com, jiri@resnulli.us,
	netdev@vger.kernel.org
Subject: Re: [PATCH net] net/sched: taprio: unwind the netdevice notifier if register_qdisc() fails
Date: Thu, 22 Oct 2026 12:59:41 +0800	[thread overview]
Message-ID: <4E594EF6-5635-44DD-91B5-D98A6FDDA49F@gmail.com> (raw)
In-Reply-To: <179259829934.3290.5380861866339404482@kernel.org>

Hi, The issue was found by LLM-assisted review of this code path (static analysis), not from a production hit or a syzbot report. I then wrote a reproducer and ran it on an arm64 QEMU guest under KASAN; it fired at the claimed sink (notifier_call_chain, vmalloc-out-of-bounds). The "Assisted-by: LLM" trailer reflects that assistance. Thanks.

> 2026年10月21日 下午11:58,netdev-bot+sinfo@kernel.org 写道:
> 
> Hi!
> 
> This is an automated message. This series looks like a fix, but its
> commit messages seem to be missing some information:
> 
> - How the issue was discovered, e.g. hit in production, hit during
>   development, syzbot report, manual code inspection, LLM or static
>   analysis tool scan.
> 
> Please do not repost the series just to address the above. Instead,
> reply to this email with the missing information, so that reviewers
> can take it into account. If the series needs another revision for
> other reasons, please include the information in the commit messages
> then.
> 
> The evaluation is done by an LLM so it may be wrong, if you think
> that is the case please reply and explain.


  reply	other threads:[~2026-10-22  5:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 15:54 [PATCH net] net/sched: taprio: unwind the netdevice notifier if register_qdisc() fails Dudu Lu
2026-10-21 15:58 ` netdev-bot+sinfo
2026-10-22  4:59   ` phx [this message]
2026-10-23 10:59 ` Simon Horman
2026-10-26 23:30 ` patchwork-bot+netdevbpf

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=4E594EF6-5635-44DD-91B5-D98A6FDDA49F@gmail.com \
    --to=phx0fer@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=netdev-bot+sinfo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vinicius.gomes@intel.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