On Sun, Nov 15, 2026 at 12:08 PM [off-list ref] 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.
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.
*IMPORTANT*: If you do repost (for other reasons) - please include
the relevant info in the cover letter or commit messages.
--
The evaluation is done by an LLM so it may be wrong, if you think
that is the case please reply and explain.
Ugh, I think I dropped this description somehow. These are follow up
fixes to my earlier series that fixed the device getting revoked for
non-leased devices, where criticality high issues were called out for
leased devices. Not hit in production. It's sashiko code review issues
that are correct from reviewing the code. Not reproduced on real
hardware.
--
Thanks,
Mina