On Thu, Oct 01, 2026 at 06:28:58PM +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:
- 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.
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.
It seems to me that while a KSAN trace is provided for patch 1/2,
it would be helpful to describe more explicitly a case where this arises.
And for patch 2/2 it is unclear to me if this is theoretical or not.
Weiming could you provide more information for both patches?