From: David Ahern <dsahern@gmail.com>
To: Florian Westphal <fw@strlen.de>, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] mptcp: avoid uninitialised errno usage
Date: Sun, 9 May 2021 16:11:11 -0600 [thread overview]
Message-ID: <b8d9cc70-7667-d2b3-50b6-0ef0ce041735@gmail.com> (raw)
In-Reply-To: <20210503103631.30694-1-fw@strlen.de>
On 5/3/21 4:36 AM, Florian Westphal wrote:
> The function called *might* set errno based on errno value in NLMSG_ERROR
> message, but in case no such message exists errno is left alone.
>
> This may cause ip to fail with
> "can't subscribe to mptcp events: Success"
>
> on kernels that support mptcp but lack event support (all kernels <= 5.11).
>
> Set errno to a meaningful value. This will then still exit with the
> more specific 'permission denied' or some such when called by process
> that lacks CAP_NET_ADMIN on 5.12 and later.
>
> Fixes: ff619e4fd370 ("mptcp: add support for event monitoring")
> Signed-off-by: Florian Westphal <fw@strlen.de>
> ---
> ip/ipmptcp.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/ip/ipmptcp.c b/ip/ipmptcp.c
> index 5f490f0026d9..504b5b2f5329 100644
> --- a/ip/ipmptcp.c
> +++ b/ip/ipmptcp.c
> @@ -491,6 +491,9 @@ out:
>
> static int mptcp_monitor(void)
> {
> + /* genl_add_mcast_grp may or may not set errno */
> + errno = EOPNOTSUPP;
> +
> if (genl_add_mcast_grp(&genl_rth, genl_family, MPTCP_PM_EV_GRP_NAME) < 0) {
> perror("can't subscribe to mptcp events");
> return 1;
>
Seems like this should be set in genl_add_mcast_grp vs its caller.
next prev parent reply other threads:[~2021-05-09 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 10:36 [PATCH iproute2] mptcp: avoid uninitialised errno usage Florian Westphal
2021-05-09 22:11 ` David Ahern [this message]
2021-05-09 22:25 ` Florian Westphal
2021-05-09 22:44 ` David Ahern
2021-05-09 22:55 ` Florian Westphal
2021-05-09 23:38 ` David Ahern
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=b8d9cc70-7667-d2b3-50b6-0ef0ce041735@gmail.com \
--to=dsahern@gmail.com \
--cc=fw@strlen.de \
--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