From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pablo Neira Ayuso Subject: Re: [PATCH 2/2] conntrack: snprintf: add connlabel format specifier Date: Thu, 20 Jun 2013 13:50:52 +0200 Message-ID: <20130620115052.GB7070@localhost> References: <1371588862-3407-1-git-send-email-fw@strlen.de> <1371588862-3407-2-git-send-email-fw@strlen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netfilter-devel@vger.kernel.org To: Florian Westphal Return-path: Received: from mail.us.es ([193.147.175.20]:47076 "EHLO mail.us.es" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965044Ab3FTLu7 (ORCPT ); Thu, 20 Jun 2013 07:50:59 -0400 Content-Disposition: inline In-Reply-To: <1371588862-3407-2-git-send-email-fw@strlen.de> Sender: netfilter-devel-owner@vger.kernel.org List-ID: On Tue, Jun 18, 2013 at 10:54:22PM +0200, Florian Westphal wrote: > by default, nfct_snprintf will not resolve connlabel names, as they're > system specific. This adds a fmt attribute to resolve names accordingly. > > output looks like this: > ... mark=0 use=1 labels=eth0-in (0),eth1-in (1) > or > > I think that the bit field is meaningless, so I would just export the strings. I'd use: I'd rather use elements, attributes are not easily extensible IMO. > Major stupidity: > As names can be anything, we need to be careful, especially when > creating XML output. Only alphanumerical label names are printed at > this time. Hm, the string is enclosed between commas, isn't that enough to avoid troubles? > Else you get > labels=(0), .. or