On Fri, Oct 05, 2018 at 01:25:22PM -0600, David Ahern wrote:

On 10/5/18 11:48 AM, Christian Brauner wrote:

quoted

On Thu, Oct 04, 2018 at 02:33:46PM -0700, David Ahern wrote:

quoted

From: David Ahern <redacted>

Update inet6_dump_ifinfo for strict data checking. If the flag is
set, the dump request is expected to have an ifinfomsg struct as
the header. All elements of the struct are expected to be 0 and no
attributes can be appended.

Signed-off-by: David Ahern <redacted>

Acked-by: Christian Brauner <christian@brauner.io>

quoted

This is on top of current net-next? Are your patches ensuring that
ipv6 addr requests don't generate log messages anymore when a wrong
header is passed but the strict socket option is not passed? The context
here doesn't seem to indicate that. :)

this is an AF_INET6 GETLINK handler. Why? no idea, but I think you are
confusing this patch with the GETADDR patch which generated the
"netlink: 16 bytes leftover after parsing attributes in process `ip'."
message before this set.

Yes, I realized this immediately afterwards.