From: David Miller <davem@davemloft.net>
To: mkubecek@suse.cz
Cc: netdev@vger.kernel.org, dsahern@gmail.com,
johannes.berg@intel.com, jiri@mellanox.com, pablo@netfilter.org,
kadlec@blackhole.kfki.hu, fw@strlen.de,
netfilter-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] make nla_nest_start() add NLA_F_NESTED flag
Date: Sat, 27 Apr 2019 17:04:02 -0400 (EDT) [thread overview]
Message-ID: <20190427.170402.1871506886672225679.davem@davemloft.net> (raw)
In-Reply-To: <cover.1556269635.git.mkubecek@suse.cz>
From: Michal Kubecek <mkubecek@suse.cz>
Date: Fri, 26 Apr 2019 11:13:03 +0200 (CEST)
> One of the comments in recent review of the ethtool netlink series pointed
> out that proposed ethnl_nest_start() helper which adds NLA_F_NESTED to
> second argument of nla_nest_start() is not really specific to ethtool
> netlink code. That is hard to argue with as closer inspection revealed that
> exactly the same helper already exists in ipset code (except it's a macro
> rather than an inline function).
>
> Another observation was that even if NLA_F_NESTED flag was introduced in
> 2007, only few netlink based interfaces set it in kernel generated messages
> and even many recently added APIs omit it. That is unfortunate as without
> the flag, message parsers not familiar with attribute semantics cannot
> recognize nested attributes and do not see message structure; this affects
> e.g. wireshark dissector or mnl_nlmsg_fprintf() from libmnl.
>
> This is why I'm suggesting to rename existing nla_nest_start() to different
> name (nla_nest_start_noflag) and reintroduce nla_nest_start() as a wrapper
> adding NLA_F_NESTED flag. This is implemented in first patch which is
> mostly generated by spatch. Second patch drops ipset helper macros which
> lose their purpose. Third patch cleans up minor coding style issues found
> by checkpatch.pl in first patch.
>
> We could leave nla_nest_start() untouched and simply add a wrapper adding
> NLA_F_NESTED but that would probably preserve the state when even most new
> code doesn't set the flag.
Series applied, thank you.
prev parent reply other threads:[~2019-04-27 21:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 9:13 Michal Kubecek
2019-04-26 9:13 ` [PATCH net-next 1/3] netlink: " Michal Kubecek
2019-04-26 10:51 ` Jiri Pirko
2019-04-26 15:03 ` David Ahern
2019-04-26 9:13 ` [PATCH net-next 2/3] ipset: drop ipset_nest_start() and ipset_nest_end() Michal Kubecek
2019-04-26 16:59 ` Jozsef Kadlecsik
2019-04-26 9:13 ` [PATCH net-next 3/3] net: fix two coding style issues Michal Kubecek
2019-04-26 9:24 ` [PATCH net-next 0/3] make nla_nest_start() add NLA_F_NESTED flag Johannes Berg
2019-04-26 11:19 ` Michal Kubecek
2019-04-26 11:23 ` Johannes Berg
2019-04-26 11:56 ` Michal Kubecek
2019-04-26 12:17 ` Johannes Berg
2019-04-26 15:00 ` David Ahern
2019-04-26 16:02 ` Johannes Berg
2019-04-26 16:45 ` Michal Kubecek
2019-04-27 21:04 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190427.170402.1871506886672225679.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=fw@strlen.de \
--cc=jiri@mellanox.com \
--cc=johannes.berg@intel.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®