From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 17/17] netlink: Propagate errors for "dup" operations
Date: Thu, 3 Aug 2023 00:48:20 +0200 [thread overview]
Message-ID: <20230803004820.7b7967ac@elisabeth> (raw)
In-Reply-To: <20230724060936.952659-18-david@gibson.dropbear.id.au>
On Mon, 24 Jul 2023 16:09:36 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> We now detect errors on netlink "set" operations while configuring the
> pasta namespace with --config-net. However in many cases rather than
> a simple "set" we use a more complex "dup" function to copy
> configuration from the host to the namespace. We're not yet properly
> detecting and reporting netlink errors for that case.
>
> Change the "dup" operations to propagate netlink errors to their
> caller, pasta_ns_conf() and report them there.
>
> Link: https://bugs.passt.top/show_bug.cgi?id=60
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> netlink.c | 40 ++++++++++++++++++++++++++++------------
> netlink.h | 8 ++++----
> pasta.c | 15 ++++++++-------
> 3 files changed, 40 insertions(+), 23 deletions(-)
>
> diff --git a/netlink.c b/netlink.c
> index 9e72b16..cdc18c0 100644
> --- a/netlink.c
> +++ b/netlink.c
> @@ -413,9 +413,11 @@ int nl_route_set_def(int s, unsigned int ifi, sa_family_t af, void *gw)
> * @s_dst: Netlink socket in destination namespace
> * @ifi_dst: Interface index in destination namespace
> * @af: Address family
> + *
> + * Return: 0 on success, negative error code on failure
> */
> -void nl_route_dup(int s_src, unsigned int ifi_src,
> - int s_dst, unsigned int ifi_dst, sa_family_t af)
> +int nl_route_dup(int s_src, unsigned int ifi_src,
> + int s_dst, unsigned int ifi_dst, sa_family_t af)
> {
> struct req_t {
> struct nlmsghdr nlh;
> @@ -477,9 +479,11 @@ void nl_route_dup(int s_src, unsigned int ifi_src,
>
> if (extra) {
> err("netlink: Too many routes to duplicate");
> - return;
> + return -E2BIG;
This is "Argument list too long", and... I don't have much better
ideas. I would instinctively use ENOSPC or ENOMEM in this case, but
both are slightly misleading in different ways, too.
> }
> }
> + if (status < 0)
> + return status;
>
> /* Routes might have dependencies between each other, and the
> * kernel processes RTM_NEWROUTE messages sequentially. For n
> @@ -494,15 +498,20 @@ void nl_route_dup(int s_src, unsigned int ifi_src,
> NLMSG_OK(nh, status);
> nh = NLMSG_NEXT(nh, status)) {
> uint16_t flags = nh->nlmsg_flags;
> + int rc;
>
> if (nh->nlmsg_type != RTM_NEWROUTE)
> continue;
>
> - nl_do(s_dst, nh, RTM_NEWROUTE,
> - (flags & ~NLM_F_DUMP_FILTERED) | NLM_F_CREATE,
> - nh->nlmsg_len);
> + rc = nl_do(s_dst, nh, RTM_NEWROUTE,
> + (flags & ~NLM_F_DUMP_FILTERED) | NLM_F_CREATE,
> + nh->nlmsg_len);
> + if (rc < 0 && rc != -ENETUNREACH && rc != -EEXIST)
> + return rc;
> }
> }
> +
> + return 0;
> }
>
> /**
> @@ -635,9 +644,11 @@ int nl_addr_set(int s, unsigned int ifi, sa_family_t af,
> * @s_dst: Netlink socket in destination network namespace
> * @ifi_dst: Interface index in destination namespace
> * @af: Address family
> + *
> + * Return: 0 on success, negative error code on failure
> */
> -void nl_addr_dup(int s_src, unsigned int ifi_src,
> - int s_dst, unsigned int ifi_dst, sa_family_t af)
> +int nl_addr_dup(int s_src, unsigned int ifi_src,
> + int s_dst, unsigned int ifi_dst, sa_family_t af)
> {
> struct req_t {
> struct nlmsghdr nlh;
> @@ -651,6 +662,7 @@ void nl_addr_dup(int s_src, unsigned int ifi_src,
> struct nlmsghdr *nh;
> ssize_t status;
> uint16_t seq;
> + int rc= 0;
Missing whitespace.
--
Stefano
next prev parent reply other threads:[~2023-08-02 22:50 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
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 [this message]
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=20230803004820.7b7967ac@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).