From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Graf Subject: Re: [PATCH 2/2] netlink: Diag core and basic socket info dumping Date: Thu, 21 Mar 2013 12:52:30 +0000 Message-ID: <20130321125230.GB9046@casper.infradead.org> References: <1363857669-19990-1-git-send-email-avagin@openvz.org> <1363857669-19990-3-git-send-email-avagin@openvz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, "David S. Miller" , Eric Dumazet , Pavel Emelyanov , Pablo Neira Ayuso , "Eric W. Biederman" , Gao feng To: Andrey Vagin Return-path: Content-Disposition: inline In-Reply-To: <1363857669-19990-3-git-send-email-avagin@openvz.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On 03/21/13 at 01:21pm, Andrey Vagin wrote: > diff --git a/include/uapi/linux/netlink_diag.h b/include/uapi/linux/netlink_diag.h > new file mode 100644 > index 0000000..9328866 > --- /dev/null > +++ b/include/uapi/linux/netlink_diag.h > +enum { > + NETLINK_DIAG_MEMINFO, > + NETLINK_DIAG_GROUPS, > + > + NETLINK_DIAG_MAX, > +}; Please follow the common pattern and define NETLINK_DIAG_MAX as NETLINK_DIAG_GROUPS like other by doing> [...] __NETLINK_DIAG_MAX, }; #define NETLINK_DIAG_MAX (__NETLINK_DIAG_MAX - 1) Everyone is used to do: struct nlattr *attrs[NETLINK_DIAG_MAX+1]; nla_parse([...], NETLINK_DIAG_MAX, [...] In fact, the follow-up patch to ss is buggy because of this. UNIX_DIAG_MAX suffers from the same problem which is problem the cause for this.