# Re: \[RFC 0/4\] netlink: binary attribute range validation

- From: David Miller \<davem@davemloft.net\>
- Date: 2020-08-08 21:07:57 
- List: netdev
- Page: https://ratatoskr.run/netdev/2020/08/11178687
- Thread: https://ratatoskr.run/linux-wireless/2020/08/11178583/t.md

```text
From: Johannes Berg <johannes@sipsolutions.net>
Date: Wed,  5 Aug 2020 16:03:20 +0200

> This is something I'd been thinking about for a while; we already
> have NLA_MIN_LEN, NLA_BINARY (with a max len), and NLA_EXACT_LEN,
> but in quite a few places (as you can see in the last patch here)
> we need a range, and we already have a way to encode ranges for
> integer ranges, so it's pretty easy to use that for binary length
> ranges as well.
> 
> So at least for wireless this seems useful to save some code, and
> to (mostly) expose the actual limits to userspace via the policy
> export that we have now.
> 
> What do you think?

This looks great to me.
```
