From: Fernando Fernandez Mancera <fmancera@suse.de>
To: Brian Haley <haleyb.dev@gmail.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, dsahern@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 1/2 net-next v2] ipv6: use the right ifindex when replying to icmpv6 from localhost
Date: Thu, 8 Jan 2026 12:27:23 +0100 [thread overview]
Message-ID: <f308ff67-5de1-452a-999c-e9230fc31e35@suse.de> (raw)
In-Reply-To: <099019ee-05f4-457b-a82b-0fac55d8dd48@gmail.com>
On 1/7/26 6:05 PM, Brian Haley wrote:
> Hi Fernando,
>
> On 1/7/26 10:38 AM, Fernando Fernandez Mancera wrote:
>> When replying to a ICMPv6 echo request that comes from localhost address
>> the right output ifindex is 1 (lo) and not rt6i_idev dev index. Use the
>> skb device ifindex instead. This fixes pinging to a local address from
>> localhost source address.
>>
>> $ ping6 -I ::1 2001:1:1::2 -c 3
>> PING 2001:1:1::2 (2001:1:1::2) from ::1 : 56 data bytes
>> 64 bytes from 2001:1:1::2: icmp_seq=1 ttl=64 time=0.037 ms
>> 64 bytes from 2001:1:1::2: icmp_seq=2 ttl=64 time=0.069 ms
>> 64 bytes from 2001:1:1::2: icmp_seq=3 ttl=64 time=0.122 ms
>>
>> 2001:1:1::2 ping statistics
>> 3 packets transmitted, 3 received, 0% packet loss, time 2032ms
>> rtt min/avg/max/mdev = 0.037/0.076/0.122/0.035 ms
>>
>> Fixes: 1b70d792cf67 ("ipv6: Use rt6i_idev index for echo replies to a
>> local address")
>> Signed-off-by: Fernando Fernandez Mancera <fmancera@suse.de>
>> ---
>> v2: no changes
>> ---
>> net/ipv6/icmp.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/net/ipv6/icmp.c b/net/ipv6/icmp.c
>> index 5d2f90babaa5..5de254043133 100644
>> --- a/net/ipv6/icmp.c
>> +++ b/net/ipv6/icmp.c
>> @@ -965,7 +965,9 @@ static enum skb_drop_reason
>> icmpv6_echo_reply(struct sk_buff *skb)
>> fl6.daddr = ipv6_hdr(skb)->saddr;
>> if (saddr)
>> fl6.saddr = *saddr;
>> - fl6.flowi6_oif = icmp6_iif(skb);
>> + fl6.flowi6_oif = ipv6_addr_type(&fl6.daddr) & IPV6_ADDR_LOOPBACK ?
>> + skb->dev->ifindex :
>> + icmp6_iif(skb);
>> fl6.fl6_icmp_type = type;
>> fl6.flowi6_mark = mark;
>> fl6.flowi6_uid = sock_net_uid(net, NULL);
>
> Using ipv6_addr_loopback(&fl6.daddr) might be more efficient as it does
> a direct comparison of the address.
>
Yes, I think you are right.
Thanks!
Fernando.
> -Brian
>
prev parent reply other threads:[~2026-01-08 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 15:38 [PATCH 1/2 net-next v2] ipv6: use the right ifindex when replying to icmpv6 from localhost Fernando Fernandez Mancera
2026-01-07 15:38 ` [PATCH 2/2 net-next v2] selftests: ipv6_icmp: add tests for ICMPv6 handling Fernando Fernandez Mancera
2026-01-07 16:41 ` David Ahern
2026-01-08 11:24 ` Fernando Fernandez Mancera
2026-01-08 15:20 ` David Ahern
2026-01-20 19:24 ` Fernando Fernandez Mancera
2026-01-20 19:44 ` Fernando Fernandez Mancera
2026-01-07 17:05 ` [PATCH 1/2 net-next v2] ipv6: use the right ifindex when replying to icmpv6 from localhost Brian Haley
2026-01-08 11:27 ` Fernando Fernandez Mancera [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=f308ff67-5de1-452a-999c-e9230fc31e35@suse.de \
--to=fmancera@suse.de \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=haleyb.dev@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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