On Thu, Sep 07, 2023 at 11:24:02AM +0200, Maxime Chevallier wrote:
> +#define PHY_MAX_ENTRIES 16
> +
> +struct phy_list_reply_data {
> + struct ethnl_reply_data base;
> + u8 n_phys;
> + u32 phy_indices[PHY_MAX_ENTRIES];
Please could you detail the decision making behind 16 entries - is this
arbitary or based on something?
Also, please consider what we should do if we happen to have more than
16 entries.
Finally, using u8 before an array of u32 can leave 3 bytes of padding.
It would be better to use u32 for n_phys to avoid that padding.
> + mutex_lock(&phy_ns->ns_lock);
> + list_for_each_entry(phydev, &phy_ns->phys, node)
> + data->phy_indices[data->n_phys++] = phydev->phyindex;
I think this loop should limit its iterations to ensure that the
array can't overflow.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!