From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 10/17] netlink: Add nl_do() helper for simple operations with error checking
Date: Thu, 3 Aug 2023 00:48:07 +0200 [thread overview]
Message-ID: <20230803004807.7d9eb817@elisabeth> (raw)
In-Reply-To: <20230724060936.952659-11-david@gibson.dropbear.id.au>
On Mon, 24 Jul 2023 16:09:29 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> So far we never checked for errors reported on netlink operations via
> NLMSG_ERROR messages. This has led to several subtle and tricky to debug
> situations which would have been obvious if we knew that certain netlink
> operations had failed.
>
> Introduce a nl_do() helper that performs netlink "do" operations (that is
> making a single change without retreiving complex information) with much
> more thorough error checking. As well as returning an error code if we
> get an NLMSG_ERROR message, we also check for unexpected behaviour in
> several places. That way if we've made a mistake in our assumptions about
> how netlink works it should result in a clear error rather than some subtle
> misbehaviour.
>
> We update those calls to nl_req() that can use the new wrapper to do so.
> We will extend those to better handle errors in future. We don't touch
> non-"do" operations for now, those are a bit trickier.
>
> Link: https://bugs.passt.top/show_bug.cgi?id=60
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> netlink.c | 59 ++++++++++++++++++++++++++++++++++++++++++++-----------
> 1 file changed, 47 insertions(+), 12 deletions(-)
>
> diff --git a/netlink.c b/netlink.c
> index 3170344..cdd65c0 100644
> --- a/netlink.c
> +++ b/netlink.c
> @@ -148,6 +148,47 @@ static ssize_t nl_req(int s, char *buf, void *req,
> return n;
> }
>
> +/**
> + * nl_do() - Send netlink "do" request, and wait for acknowledgement
> + * @s: Netlink socket
> + * @req: Request (will fill netlink header)
> + * @type: Request type
> + * @flags: Extra request flags (NLM_F_REQUEST and NLM_F_ACK assumed)
> + * @len: Request length
> + *
> + * Return: 0 on success, negative error code on error
> + */
> +static int nl_do(int s, void *req, uint16_t type, uint16_t flags, ssize_t len)
> +{
> + struct nlmsghdr *nh;
> + char buf[NLBUFSIZ];
> + uint16_t seq;
> + ssize_t n;
> +
> + n = nl_req(s, buf, req, type, flags, len);
> + seq = ((struct nlmsghdr *)req)->nlmsg_seq;
> +
> + for (nh = (struct nlmsghdr *)buf;
> + NLMSG_OK(nh, n); nh = NLMSG_NEXT(nh, n)) {
> + struct nlmsgerr *errmsg;
> +
> + if (nh->nlmsg_seq != seq)
> + die("netlink: Unexpected response sequence number");
> +
> + switch (nh->nlmsg_type) {
> + case NLMSG_DONE:
> + return 0;
> + case NLMSG_ERROR:
> + errmsg = (struct nlmsgerr *)NLMSG_DATA(nh);
> + return errmsg->error;
This is an errno, we should probably print it here ...and, now reading
14/17 and 16/17: saving repeated strerror() calls there. On the other
hand this has the advantage of one single error message instead of two,
but... hmm.
--
Stefano
next prev parent reply other threads:[~2023-08-02 22:48 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 6:09 [PATCH 00/17] netlink fixes and cleanups David Gibson
2023-07-24 6:09 ` [PATCH 01/17] netlink: Split up functionality if nl_link() David Gibson
2023-08-02 22:47 ` Stefano Brivio
2023-08-03 2:09 ` David Gibson
2023-08-03 4:29 ` David Gibson
2023-08-03 5:39 ` David Gibson
2023-08-03 5:40 ` Stefano Brivio
2023-07-24 6:09 ` [PATCH 02/17] netlink: Split nl_addr() into separate operation functions David Gibson
2023-08-02 22:47 ` Stefano Brivio
2023-08-03 2:11 ` David Gibson
2023-07-24 6:09 ` [PATCH 03/17] netlink: Split nl_route() " David Gibson
2023-08-02 22:47 ` Stefano Brivio
2023-08-03 2:18 ` David Gibson
2023-07-24 6:09 ` [PATCH 04/17] netlink: Use struct in_addr for IPv4 addresses, not bare uint32_t David Gibson
2023-07-24 6:09 ` [PATCH 05/17] netlink: Explicitly pass netlink sockets to operations David Gibson
2023-07-24 6:09 ` [PATCH 06/17] netlink: Make nl_*_dup() use a separate datagram for each request David Gibson
2023-07-24 6:09 ` [PATCH 07/17] netlink: Start sequence number from 1 instead of 0 David Gibson
2023-07-24 6:09 ` [PATCH 08/17] netlink: Treat send() or recv() errors as fatal David Gibson
2023-08-02 22:47 ` Stefano Brivio
2023-08-03 2:19 ` David Gibson
2023-07-24 6:09 ` [PATCH 09/17] netlink: Fill in netlink header fields from nl_req() David Gibson
2023-07-24 6:09 ` [PATCH 10/17] netlink: Add nl_do() helper for simple operations with error checking David Gibson
2023-08-02 22:48 ` Stefano Brivio [this message]
2023-08-03 2:24 ` David Gibson
2023-07-24 6:09 ` [PATCH 11/17] netlink: Clearer reasoning about the netlink response buffer size David Gibson
2023-08-02 22:48 ` Stefano Brivio
2023-08-03 2:22 ` David Gibson
2023-07-24 6:09 ` [PATCH 12/17] netlink: Split nl_req() to allow processing multiple response datagrams David Gibson
2023-07-24 6:09 ` [PATCH 13/17] netlink: Add nl_foreach_oftype to filter response message types David Gibson
2023-07-24 6:09 ` [PATCH 14/17] netlink: Propagate errors for "set" operations David Gibson
2023-07-24 6:09 ` [PATCH 15/17] netlink: Always process all responses to a netlink request David Gibson
2023-07-24 6:09 ` [PATCH 16/17] netlink: Propagate errors for "dump" operations David Gibson
2023-07-24 6:09 ` [PATCH 17/17] netlink: Propagate errors for "dup" operations David Gibson
2023-08-02 22:48 ` Stefano Brivio
2023-08-03 2:26 ` David Gibson
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=20230803004807.7d9eb817@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).