From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Benc Subject: Re: netlink: 16 bytes leftover after parsing attributes in process `ip'. Date: Wed, 26 Sep 2018 07:51:15 +0200 Message-ID: <20180926075115.4ca7c527@redhat.com> References: <6059bf4e-b1cf-2c7e-5529-9003bdd8a14b@gmail.com> <20180925094908.yuu5bsrazkiq3ihy@brauner.io> <20180925164715.338bb059@redhat.com> <02fbfcb8-537c-dc5c-52dc-0f53d7fd0482@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Christian Brauner , "netdev@vger.kernel.org" , David Miller To: David Ahern Return-path: Received: from mx1.redhat.com ([209.132.183.28]:57398 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726319AbeIZMCe (ORCPT ); Wed, 26 Sep 2018 08:02:34 -0400 In-Reply-To: <02fbfcb8-537c-dc5c-52dc-0f53d7fd0482@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: On Tue, 25 Sep 2018 09:37:41 -0600, David Ahern wrote: > For ifaddrmsg ifa_flags aligns with ifi_type which is set by kernel side > so this should be ok. Does the existing user space set ifi_type to anything? Does it zero out the field? Are we able to find a flag value that is not going to be set by unaware user space? I.e., a bit that is unused by the current ARPHRD values on both little and big endian? (ARPHRD_NONE might be a problem, though...) Jiri