mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: liamsmith827 <liamsmith827@grapheneos.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-next v5 0/4] ipv4: restrict on-link fallback to lookup misses
Date: Fri, 20 Nov 2026 02:30:11 +0000	[thread overview]
Message-ID: <179514181152.3985754.6093417150310548869.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261116202741.13106-1-liamsmith827@grapheneos.org>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 16 Nov 2026 20:27:37 +0000 you wrote:
> From: Liam Smith <liamsmith827@proton.me>
> 
> When an output interface is specified (e.g., using SO_BINDTODEVICE,
> IP_UNICAST_IF or IP_PKTINFO) and the FIB lookup fails, the IPv4 output
> path ignores the error and constructs an on-link route via the
> specified interface. According to the comment above the code, the
> intent was to allow sending packets via an interface that does not have
> any routes.
> 
> [...]

Here is the summary with links:
  - [net-next,v5,1/4] ipv4: add FIB_LOOKUP_REPORT_MISS
    https://git.kernel.org/netdev/net-next/c/ebcfb8e24044
  - [net-next,v5,2/4] ipv4: restrict on-link fallback to lookup misses
    https://git.kernel.org/netdev/net-next/c/67de0b38f68a
  - [net-next,v5,3/4] selftests: net: test restricted on-link fallback
    https://git.kernel.org/netdev/net-next/c/854ec14f9360
  - [net-next,v5,4/4] ipv4: replace obsolete routing comment
    https://git.kernel.org/netdev/net-next/c/8acc01b5b851

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-20  2:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 20:27 liamsmith827
2026-11-16 20:27 ` [PATCH net-next v5 1/4] ipv4: add FIB_LOOKUP_REPORT_MISS liamsmith827
2026-11-16 20:27 ` [PATCH net-next v5 2/4] ipv4: restrict on-link fallback to lookup misses liamsmith827
2026-11-18 23:28   ` netdev-bot+sashiko
2026-11-19 15:20     ` Ido Schimmel
2026-11-16 20:27 ` [PATCH net-next v5 3/4] selftests: net: test restricted on-link fallback liamsmith827
2026-11-18 23:28   ` netdev-bot+sashiko
2026-11-16 20:27 ` [PATCH net-next v5 4/4] ipv4: replace obsolete routing comment liamsmith827
2026-11-18 23:28   ` netdev-bot+sashiko
2026-11-19 15:20     ` Ido Schimmel
2026-11-17 10:56 ` [PATCH net-next v5 0/4] ipv4: restrict on-link fallback to lookup misses Ido Schimmel
2026-11-20  2:30 ` patchwork-bot+netdevbpf [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=179514181152.3985754.6093417150310548869.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.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@grapheneos.org \
    --cc=liamsmith827@proton.me \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®