From: liamsmith827 <liamsmith827@grapheneos.org>
To: netdev-bot+sashiko@kernel.org
Cc: netdev@vger.kernel.org, dsahern@kernel.org, idosch@nvidia.com,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
liamsmith827@proton.me
Subject: Re: [PATCH net v2 2/4] ipv4: restrict on-link fallback to lookup misses
Date: Thu, 12 Nov 2026 23:08:28 +0000 [thread overview]
Message-ID: <2503cfd2-5629-448f-bb9b-111ea239efb6@grapheneos.org> (raw)
In-Reply-To: <179451823511.2199510.15480690224597348773@kernel.org>
On 11/12/26 21:17, netdev-bot+sashiko@kernel.org wrote:
> - [High] The fix is incomplete for route-based restrictions.
This is not a legitimate issue. A RT_SCOPE_UNIVERSE route not matching a
RT_SCOPE_LINK lookup is expected. Route maintainers should install the
correct routes. An unprivileged process can influence which rules/routes
are matched in many ways other than MSG_DONTROUTE.
next prev parent reply other threads:[~2026-11-12 23:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 6:15 [PATCH net v2 0/4] ipv4: restrict on-link fallback to lookup misses liamsmith827
2026-11-10 6:15 ` [PATCH net v2 1/4] ipv4: add FIB_LOOKUP_REPORT_MISS liamsmith827
2026-11-12 19:33 ` Ido Schimmel
2026-11-10 6:15 ` [PATCH net v2 2/4] ipv4: restrict on-link fallback to lookup misses liamsmith827
2026-11-12 17:38 ` Jakub Kicinski
2026-11-12 21:17 ` netdev-bot+sashiko
2026-11-12 23:08 ` liamsmith827 [this message]
2026-11-10 6:15 ` [PATCH net v2 3/4] selftests: net: test restricted on-link fallback liamsmith827
2026-11-10 6:15 ` [PATCH net v2 4/4] ipv4: replace obsolete routing comment liamsmith827
2026-11-12 21:17 ` netdev-bot+sashiko
2026-11-12 23:10 ` liamsmith827
2026-11-12 17:13 ` [PATCH net v2 0/4] ipv4: restrict on-link fallback to lookup misses Ido Schimmel
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=2503cfd2-5629-448f-bb9b-111ea239efb6@grapheneos.org \
--to=liamsmith827@grapheneos.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=liamsmith827@proton.me \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev-bot+sashiko@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