From: "Jérémy Jean" <jeremy.jean@oss.cyber.gouv.fr>
To: Simon Horman <horms@kernel.org>
Cc: netdev-bot+sinfo@kernel.org,
Subash Abhinov Kasiviswanathan
<subash.a.kasiviswanathan@oss.qualcomm.com>,
Sean Tranchetti <sean.tranchetti@oss.qualcomm.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net] net: qualcomm: rmnet: bound TX aggregates on byte-limit update
Date: Sun, 08 Nov 2026 15:36:01 +0100 [thread overview]
Message-ID: <5a28b58c53e167ea8b6e0218fb63f54f@oss.cyber.gouv.fr> (raw)
In-Reply-To: <20261108141812.GA18859@horms.kernel.org>
On 2026-11-08 15:18, Simon Horman wrote:
> On Sat, Oct 31, 2026 at 10:13:43PM +0000, netdev-bot+sinfo@kernel.org
> wrote:
>> 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.
>>
>> - Whether the issue was actually triggered, or is only theoretical
>> (e.g. found by code inspection). If it was triggered please include
>> the symptoms, like the stack trace or error messages.
>>
>> - What hardware the change was tested on. For driver fixes please
>> mention the device (and if relevant firmware version) used for
>> testing, or say that the change was not tested on real hardware.
>>
>> 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.
>
> Hi Jérémy,
>
> I would appreciate it if you could take a moment to respond to
> the questions posed by the bot above.
Hello Simon,
Sure, here are some answers:
* The bug was found by LLM-assisted code review.
* The bug was triggered by a software reproducer with a KASAN enabled
kernel under QEMU VM.
* It has not been tested on real hardware.
Regards,
Jérémy
next prev parent reply other threads:[~2026-11-08 14:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 22:10 [PATCH net] net: qualcomm: rmnet: avoid stale VND access on TX drop Jérémy Jean
2026-10-31 22:10 ` [PATCH net] net: qualcomm: rmnet: bound TX aggregates on byte-limit update Jérémy Jean
2026-10-31 22:13 ` netdev-bot+sinfo
2026-11-08 14:18 ` Simon Horman
2026-11-08 14:36 ` Jérémy Jean [this message]
2026-11-08 16:40 ` Simon Horman
2026-11-08 7:36 ` subash.a.kasiviswanathan
2026-10-31 22:13 ` [PATCH net] net: qualcomm: rmnet: avoid stale VND access on TX drop netdev-bot+sinfo
2026-11-01 22:11 ` netdev-bot+sashiko
2026-11-01 22:59 ` Jérémy Jean
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=5a28b58c53e167ea8b6e0218fb63f54f@oss.cyber.gouv.fr \
--to=jeremy.jean@oss.cyber.gouv.fr \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sinfo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sean.tranchetti@oss.qualcomm.com \
--cc=stable@vger.kernel.org \
--cc=subash.a.kasiviswanathan@oss.qualcomm.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®