From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: a@unstable.cc, mareklindner@neomailbox.ch
Subject: Re: [B.A.T.M.A.N.] [PATCHv2] batctl: Use netlink to replace some of debugfs
Date: Tue, 03 May 2016 09:07:35 +0200 [thread overview]
Message-ID: <3295917.zMxpBmcd5T@bentobox> (raw)
In-Reply-To: <1462222618-29761-1-git-send-email-andrew@lunn.ch>
[-- Attachment #1: Type: text/plain, Size: 2310 bytes --]
[...]
> +ifeq ($(origin LIBNL_GENL_CFLAGS) $(origin LIBNL_GENL_LDLIBS), undefined undefined)
> + LIBNL_GENL_NAME ?= libnl-genl-3.0
> + ifeq ($(shell $(PKG_CONFIG) --modversion $(LIBNL_GENL_NAME) 2>/dev/null),)
> + $(error No $(LIBNL_GENL_NAME) development libraries found!)
> + endif
> + LIBNL_GENL_CFLAGS += $(shell $(PKG_CONFIG) --cflags $(LIBNL_GENL_NAME))
> + LIBNL_GENL_LDLIBS += $(shell $(PKG_CONFIG) --libs $(LIBNL_GENL_NAME))
> +endif
> +CFLAGS += $(LIBNL_GENL_CFLAGS)
> +LDLIBS += $(LIBNL_GENL_LDLIBS)
@Simon, @Matthias, @Antonio, @Marek: Should the header file be included in
batctl like nl80211.h in iw. Or should we always require the current kernel
header files installed to build batctl?
[...]
> +struct mandatory_attr {
> + int attr;
> + int datalen;
> +};
> +
> +static int last_err;
> +
> +static int invalidate_mandatory_attrs(struct nlattr *attrs[],
> + const struct mandatory_attr *mandatory[],
> + int num)
> +{
> + int i;
> + int len;
> +
> + for (i = 0; i < num; i++) {
> + if (!attrs[mandatory[i]->attr])
> + return EINVAL;
> + len = nla_len(attrs[mandatory[i]->attr]);
> + if (mandatory[i]->datalen && (len != mandatory[i]->datalen))
> + return EINVAL;
> + }
> +
> + return 0;
> +}
> +
> +static const struct mandatory_attr mandatory_attr_version= {
> + BATADV_ATTR_VERSION, 0 };
[...]
> +static const struct mandatory_attr *info_hard_mandatory[] = {
> + &mandatory_attr_version,
> + &mandatory_attr_algo_name,
> + &mandatory_attr_hard_ifname,
> + &mandatory_attr_hard_address,
> +};
> +
> +static int info_callback(struct nl_msg *msg, void *arg __unused)
> +{
[...]
> + if (nla_parse(attrs, BATADV_ATTR_MAX, genlmsg_attrdata(ghdr, 0),
> + genlmsg_len(ghdr), NULL)) {
> + fputs("Received invalid data from kernel.", stderr);
> + exit(1);
> + }
> +
> + if (invalidate_mandatory_attrs(attrs, info_mandatory,
> + ARRAY_SIZE(info_mandatory))) {
> + fputs("Missing/invalid attributes from kernel\n", stderr);
> + exit(1);
> + }
Interesting idea to check the mandatory attributes with a common function. But
shouldn't be the length checked by the nl_parse(..., policy) [1]? This is
especially important because you don't check the type.
Kind regards,
Sven
[1] http://www.infradead.org/~tgr/libnl/doc/core.html#core_attr_validation
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-05-03 7:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 20:56 [B.A.T.M.A.N.] [PATCHv2] batctl: Use netlink to replace some of debugfs Andrew Lunn
2016-05-03 7:07 ` Sven Eckelmann [this message]
2016-05-03 12:20 ` Andrew Lunn
2016-05-03 12:26 ` Sven Eckelmann
2016-05-03 12:47 ` Andrew Lunn
2016-05-03 12:54 ` Sven Eckelmann
2016-05-03 13:08 ` Andrew Lunn
2016-05-03 20:16 ` Marek Lindner
2016-05-03 20:30 ` Andrew Lunn
2016-05-03 9:47 ` Sven Eckelmann
2016-05-03 9:51 ` Sven Eckelmann
2016-05-03 10:30 ` Sven Eckelmann
2016-05-03 12:45 ` Andrew Lunn
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=3295917.zMxpBmcd5T@bentobox \
--to=sven@narfation.org \
--cc=a@unstable.cc \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=mareklindner@neomailbox.ch \
/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