On Tue, 21 Jul 2026 01:42:55 +0000 Deep Shah wrote:
> The caller already has write access to the PHC, so this hardens the
> max_adj sanity check rather than crossing a privilege boundary, and
> well-behaved user space (e.g. ptp4l) never requests such values. It is
> a follow-up to commit 475b92f93216 ("ptp: improve max_adj check against
> unreasonable values"), which handled the analogous s32 narrowing but not
> this multiplication overflow.
Exactly, so I think this sort of patch belongs in net-next without
a Fixes tags. Because _nobody cares_. Please correct me if I'm wrong.
