netdev - Re: [PATCH] ipv6: socket SO_BINDTODEVICE lookup routing fail without IPv6 rule.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <dfd37ca0-14c6-4cc1-8fae-f1aa2d23e148@kernel.org>
Date: Thu, 2 Jan 2025 08:57:17 -0700
From: David Ahern <dsahern@...nel.org>
To: shiming cheng <shiming.cheng@...iatek.com>,
 willemdebruijn.kernel@...il.com, davem@...emloft.net, edumazet@...gle.com,
 kuba@...nel.org, pabeni@...hat.com, horms@...nel.org,
 matthias.bgg@...il.com, angelogioacchino.delregno@...labora.com,
 linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 linux-mediatek@...ts.infradead.org
Cc: netdev@...r.kernel.org, lena.wang@...iatek.com
Subject: Re: [PATCH] ipv6: socket SO_BINDTODEVICE lookup routing fail without
 IPv6 rule.

On 1/2/25 2:51 AM, shiming cheng wrote:
>      When using socket IPv6 with SO_BINDTODEVICE, if IPv6 rule is not
>         matched, it will return ENETUNREACH. In fact, IPv4 does not behave
>         this way. IPv4 prioritizes looking up IP rules for routing and
>         forwarding, if not matched it will use socket-bound out interface
>         to send packets. The modification here is to make IPv6 behave the
>         same as IPv4. If IP rule is not found, it will also use
>         socket-bound out interface to send packts.
> 

Please create test cases for IPv4 and IPv6 showing the problem - what
you are configuring and the expected result.

Also, commit messages should align with first column unless there is a
reason for an indentation.