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: <20250103181431.536909ad@kernel.org>
Date: Fri, 3 Jan 2025 18:14:31 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Shiming Cheng <shiming.cheng@...iatek.com>
Cc: <willemdebruijn.kernel@...il.com>, <davem@...emloft.net>,
 <dsahern@...nel.org>, <edumazet@...gle.com>, <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>, <netdev@...r.kernel.org>,
 <lena.wang@...iatek.com>
Subject: Re: [PATCH net v2] ipv6: socket SO_BINDTODEVICE lookup routing fail
 without IPv6 rule.

On Fri, 3 Jan 2025 13:43:49 +0800 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.

CI shows failures in tools/testing/selftests/net/fcnal-test.sh
and tools/testing/selftests/net/fib_nexthops.sh with this patch
applied. Could be a flake but please double check before sending v3

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ