Re: [PATCH net 0/4] bnge: Fix error-path and IRQ setup bugs in probe/open
From: Bhargava Chenna Marreddy
Date: Mon Oct 05 2026 - 08:42:58 EST
Hi,
To provide the requested context for reviewers:
- Discovery: Identified during review of the "bnge: Support async
events while down" series -- three were flagged by Sashiko, and one
was flagged by Simon Horman.
- Trigger: Identified via code review and static analysis (potential
issues in failure handling and IRQ setup paths).
- Testing: Tested on physical bnge hardware; compile-tested and
verified checkpatch --strict clean.
To provide the requested context for reviewers:
- Discovery: Identified during review of the "bnge: Support async
events while down" series -- three were flagged by Sashiko, and one
was flagged by Simon Horman.
- Trigger: Identified via code review and static analysis (potential
issues in failure handling and IRQ setup paths).
- Testing: Tested on physical bnge hardware; compile-tested and
verified checkpatch --strict clean.
Regards,
Bhargava, Marreddy.
On Mon, Oct 5, 2026 at 5:53 PM <netdev-bot+sinfo@xxxxxxxxxx> 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.
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature