From: Stephen Hemminger <stephen@networkplumber.org>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: netdev@vger.kernel.org, Eric Dumazet <eric.dumazet@gmail.com>,
David Ahern <dsa@cumulusnetworks.com>,
Andrey Vagin <avagin@openvz.org>
Subject: Re: [RFC net-next iproute2 1/2] libnetlink: Add test for error code returned from netlink reply
Date: Wed, 26 Oct 2016 20:52:56 -0700 [thread overview]
Message-ID: <20161026205256.162e1d25@xeon-e3> (raw)
In-Reply-To: <1477510208-20292-2-git-send-email-gorcunov@gmail.com>
On Wed, 26 Oct 2016 22:30:07 +0300
Cyrill Gorcunov <gorcunov@gmail.com> wrote:
>
> if (h->nlmsg_type == NLMSG_DONE) {
> + int len;
> +
> + /*
> + * The kernel reports if there is
> + * no inet-diag module present in
> + * the system via negative length
> + * as error code.
> + */
> + if (h->nlmsg_len < NLMSG_LENGTH(sizeof(int))) {
> + fprintf(stderr, "Truncated length reply\n");
> + return -1;
> + }
> + len = *(int *)NLMSG_DATA(h);
> + if (len < 0) {
> + errno = -len;
> + if (errno == ENOENT ||
> + errno == EOPNOTSUPP)
> + return -1;
> + perror("RTNETLINK answers");
> + return len;
> + }
> found_done = 1;
> break; /* process next filter */
>
This looks like a mistake in how you implemented the functionality in the kernel.
Despite what it looks like, all netlink request/reply functionality reports
errors in current implementation by returning error to the sendmsg request.
What you added implies that the new kernel api is wrong, or many other usages
are wrong. Please fix the kernel.
next prev parent reply other threads:[~2016-10-27 3:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 19:30 [RFC net-next iproute2 0/2] Add support for operating raw sockest via diag interface Cyrill Gorcunov
2016-10-26 19:30 ` [RFC net-next iproute2 1/2] libnetlink: Add test for error code returned from netlink reply Cyrill Gorcunov
2016-10-27 3:52 ` Stephen Hemminger [this message]
2016-10-27 6:52 ` Cyrill Gorcunov
2016-10-27 8:24 ` Cyrill Gorcunov
2016-10-26 19:30 ` [RFC net-next iproute2 2/2] ss: Add inet raw sockets information gathering via netlink diag interface Cyrill Gorcunov
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=20161026205256.162e1d25@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=avagin@openvz.org \
--cc=dsa@cumulusnetworks.com \
--cc=eric.dumazet@gmail.com \
--cc=gorcunov@gmail.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).