From: Johannes Berg <[email protected]> Date: Mon, 31 Aug 2020 20:28:05 +0200
> From: Johannes Berg <[email protected]> > > In the policy export for binary attributes I erroneously used > a != NLA_VALIDATE_NONE comparison instead of checking for the > two possible values, which meant that if a validation function > pointer ended up aliasing the min/max as negatives, we'd hit > a warning in nla_get_range_unsigned(). > > Fix this to correctly check for only the two types that should > be handled here, i.e. range with or without warn-too-long. > > Reported-by: [email protected] > Fixes: 8aa26c575fb3 ("netlink: make NLA_BINARY validation more flexible") > Signed-off-by: Johannes Berg <[email protected]> Applied, thank you.
