From: Simon Horman <horms@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, David Ahern <dsahern@kernel.org>,
Paul Ripke <stix@google.com>,
eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 2/2] ipv6: fix blackhole routes
Date: Sun, 16 Feb 2025 09:50:05 +0000 [thread overview]
Message-ID: <20250216095005.GC1615191@kernel.org> (raw)
In-Reply-To: <20250212164323.2183023-3-edumazet@google.com>
On Wed, Feb 12, 2025 at 04:43:23PM +0000, Eric Dumazet wrote:
> For some reason, linux does not really act as a blackhole
> for local processes:
>
> ip route add blackhole 100::/64 # RFC 6666
> ip route get 100::
> RTNETLINK answers: Invalid argument
> ping6 -c2 100::
> ping6: connect: Invalid argument
> ip route del 100::/64
>
> After this patch, a local process no longer has an immediate error,
> the blackhole is simply eating the packets as intended.
>
> Also the "route get" command does not fail anymore.
>
> ip route add blackhole 100::/64
> ip route get 100::
> blackhole 100:: dev lo src ::1 metric 1024 pref medium
> ping6 -c2 100::
> PING 100:: (100::) 56 data bytes
>
> --- 100:: ping statistics ---
> 2 packets transmitted, 0 received, 100% packet loss, time 1019ms
Hi Eric,
Sorry to nit-pick on something that is nothing to do with the change
itself. But could you reformat the above somehow as git will cut off
the commit message at the ("^---") above. Which amongst other things
means the patch will end up without a Signed-off-by line in git.
>
> ip route del 100::/64
>
> Reported-by: Paul Ripke <stix@google.com>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
...
prev parent reply other threads:[~2025-02-16 9:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 16:43 [PATCH net-next 0/2] net: better support of blackholes Eric Dumazet
2025-02-12 16:43 ` [PATCH net-next 1/2] net: dropreason: add SKB_DROP_REASON_BLACKHOLE Eric Dumazet
2025-02-12 17:57 ` David Ahern
2025-02-12 16:43 ` [PATCH net-next 2/2] ipv6: fix blackhole routes Eric Dumazet
2025-02-12 18:00 ` David Ahern
2025-02-12 18:38 ` Eric Dumazet
2025-02-13 2:30 ` Stanislav Fomichev
2025-02-13 15:49 ` David Ahern
2025-02-18 8:43 ` Nicolas Dichtel
2025-02-16 9:50 ` Simon Horman [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=20250216095005.GC1615191@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stix@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.