Re: [PATCH net-next v2 0/3] net: pcs: rzn1-miic: Validate dtb configuration values

[Kyle Hendry <khendry@reliablecontrols.com>]

On 28-Sep-26 14:25, 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.

On the RZ/N1D I can trigger a KASAN slab-out-of-bounds error by defining 
miic 6 in the dts. I can also trigger a KASAN global-out-of-bounds error 
by configuring a miic input with a value outside the defined range.

I don't have a RZ/T2H to test with, but after investigating the sashiko 
reviews [1], [2] I agree that there is still a bug when checking for 
miic_port_max. If the value in rzt2h_miic_of_data is correct and being 
used as intended I can resubmit the patch using conf_conv_count instead. 
If the fixes tags were added inappropriately, I can remove them and 
resubmit this series.

[1] 
https://lore.kernel.org/all/178955899323.22033.2372714834297554596@kernel.org/
[2] 
https://lore.kernel.org/all/178955899447.22033.5754427139793967412@kernel.org/