From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pablo Neira Ayuso Subject: Re: Xtables2 Netlink spec Date: Fri, 17 Dec 2010 10:55:19 +0100 Message-ID: <4D0B3387.5030807@netfilter.org> References: <4D00C6A4.6090305@netfilter.org> <4D08C892.3080704@netfilter.org> <20101216140537.GA23297@canuck.infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit To: Jan Engelhardt , Jozsef Kadlecsik , Netfilter Developer Mailing List , netfilter@vger.kernel.org Return-path: Received: from mail.us.es ([193.147.175.20]:54235 "EHLO mail.us.es" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752437Ab0LQJzW (ORCPT ); Fri, 17 Dec 2010 04:55:22 -0500 In-Reply-To: <20101216140537.GA23297@canuck.infradead.org> Sender: netfilter-devel-owner@vger.kernel.org List-ID: On 16/12/10 15:05, Thomas Graf wrote: > On Wed, Dec 15, 2010 at 02:54:26PM +0100, Pablo Neira Ayuso wrote: >>> BTW, can response messages - all those leading up to NLMSG_DONE - >>> have different nlmsg_type, or not? >> >> They all have the same type. > > This is not a MUST. It is perfectly legal to f.e.: > > -> FOO_GET (seq=1, NLM_F_REQUEST) > <- FOO_DEL (seq=1, NLM_F_MULTI) > <- FOO_ADD (seq=1, NLM_F_MULTI) > <- NLMSG_DONE (seq=1) What realistic situation will require this?