On 5/19/20 11:02 AM, Roopa Prabhu wrote:
What are the rules here.... does neighbor code only check for NDA_NH_ID
because the strict start type is set to NDA_NH_ID ?
Lack of checking of unused attributes leads to the kernel silently
ignoring userspace data. From top of memory that has a few problems:
1. does the kernel support feature A (lack of probing for a feature),
2. kernel not implementing what the user requested and not telling the user,
3. impacting the ability to start using feature A in that code at some
point in the future (it was ignored in the past and garbage was passed
in, now suddenly that garbage is acted on).