From: Greg KH <gregkh@linuxfoundation.org>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
David Ahern <dsahern@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH 5.4-stable] ping: fix address binding wrt vrf
Date: Mon, 16 May 2022 15:16:39 +0200 [thread overview]
Message-ID: <YoJOt+AhvS/XR39B@kroah.com> (raw)
In-Reply-To: <20220516125229.32188-1-nicolas.dichtel@6wind.com>
On Mon, May 16, 2022 at 02:52:29PM +0200, Nicolas Dichtel wrote:
> commit e1a7ac6f3ba6e157adcd0ca94d92a401f1943f56 upstream.
>
> When ping_group_range is updated, 'ping' uses the DGRAM ICMP socket,
> instead of an IP raw socket. In this case, 'ping' is unable to bind its
> socket to a local address owned by a vrflite.
>
> Before the patch:
> $ sysctl -w net.ipv4.ping_group_range='0 2147483647'
> $ ip link add blue type vrf table 10
> $ ip link add foo type dummy
> $ ip link set foo master blue
> $ ip link set foo up
> $ ip addr add 192.168.1.1/24 dev foo
> $ ip addr add 2001::1/64 dev foo
> $ ip vrf exec blue ping -c1 -I 192.168.1.1 192.168.1.2
> ping: bind: Cannot assign requested address
> $ ip vrf exec blue ping6 -c1 -I 2001::1 2001::2
> ping6: bind icmp socket: Cannot assign requested address
>
> CC: stable@vger.kernel.org
> Fixes: 1b69c6d0ae90 ("net: Introduce L3 Master device abstraction")
> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
> Reviewed-by: David Ahern <dsahern@kernel.org>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
> ---
>
> The patch applies also on 4.19, 4.14 and 4.9 stable trees, but I didn't test or
> compile it on these trees.
now all queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-05-16 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 8:16 FAILED: patch "[PATCH] ping: fix address binding wrt vrf" failed to apply to 5.4-stable tree gregkh
2022-05-16 12:52 ` [PATCH 5.4-stable] ping: fix address binding wrt vrf Nicolas Dichtel
2022-05-16 13:16 ` Greg KH [this message]
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=YoJOt+AhvS/XR39B@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.