From: "Théo Lebrun" <theo.lebrun@bootlin.com>
To: <netdev-bot+sinfo@kernel.org>
Cc: "Conor Dooley" <conor.dooley@microchip.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"Nicolai Buchwitz" <nb@tipi-net.de>,
"Vladimir Kondratiev" <vladimir.kondratiev@mobileye.com>,
"Gregory CLEMENT" <gregory.clement@bootlin.com>,
"Benoît Monin" <benoit.monin@bootlin.com>,
"Tawfik Bayouk" <tawfik.bayouk@mobileye.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH net-next] net: macb: move printk() calls out of bp->lock critical section
Date: Wed, 30 Sep 2026 20:55:47 +0200 [thread overview]
Message-ID: <DLSVOPXORTQN.3VAUYHPWRAYVO@bootlin.com> (raw)
In-Reply-To: <179079351154.31693.11286897642165841220@kernel.org>
Hello netdev bot,
On Wed Sep 30, 2026 at 8:38 PM CEST, wrote:
> 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.
This is mentioned two fold; in the commit message:
The netconsole deadlock is theoretical & never reproduced.
And in the cover letter (folded below the '--' line):
Technically it is a fix, in practice I'm happy for it to go through
net-next/main for more testing and it is a theoretical bugfix (as usual
nowadays). Decided after seeing Jakub taking a similar patch into
net-next this morning:
[...]
> - 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.
I do most of my MACB tests on EyeQ5.
> 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.
I love this newly introduced message!
But here it might have been a false positive (?).
- Can it read what's below the '--' line?
- Maybe it could trust the driver maintainers, especially regarding the
second question about having access to real hardware?
I looked around to see if this infra was open-source but I couldn't find
it. Only found the https://github.com/linux-netdev/nipa repo but that's
not it.
Thanks,
--
Théo Lebrun, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-09-30 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 18:35 [PATCH net-next] net: macb: move printk() calls out of bp->lock critical section Théo Lebrun
2026-09-30 18:38 ` netdev-bot+sinfo
2026-09-30 18:55 ` Théo Lebrun [this message]
2026-10-05 23:19 ` Jakub Kicinski
2026-10-02 9:53 ` Nicolai Buchwitz
2026-10-05 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=DLSVOPXORTQN.3VAUYHPWRAYVO@bootlin.com \
--to=theo.lebrun@bootlin.com \
--cc=andrew+netdev@lunn.ch \
--cc=benoit.monin@bootlin.com \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregory.clement@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nb@tipi-net.de \
--cc=netdev-bot+sinfo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tawfik.bayouk@mobileye.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vladimir.kondratiev@mobileye.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.