From: Paolo Abeni <pabeni@redhat.com>
To: Menglong Dong <menglong8.dong@gmail.com>,
edumazet@google.com, kuba@kernel.org
Cc: davem@davemloft.net, dsahern@kernel.org,
steffen.klassert@secunet.com, herbert@gondor.apana.org.au,
dongml2@chinatelecom.cn, bigeasy@linutronix.de, toke@redhat.com,
idosch@nvidia.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/7] net: ip: add drop reasons to input route
Date: Thu, 10 Oct 2024 10:30:32 +0200 [thread overview]
Message-ID: <3c2ad895-3546-4269-8e6d-6f187035f4b5@redhat.com> (raw)
In-Reply-To: <20241007074702.249543-1-dongml2@chinatelecom.cn>
On 10/7/24 09:46, Menglong Dong wrote:
> In this series, we mainly add some skb drop reasons to the input path of
> ip routing.
>
> The errno from fib_validate_source() is -EINVAL or -EXDEV, and -EXDEV is
> used in ip_rcv_finish_core() to increase the LINUX_MIB_IPRPFILTER. For
> this case, we can check it by
> "drop_reason == SKB_DROP_REASON_IP_RPFILTER" instead. Therefore, we can
> make fib_validate_source() return -reason.
>
> Meanwhile, we make the following functions return drop reasons too:
>
> ip_route_input_mc()
> ip_mc_validate_source()
> ip_route_input_slow()
> ip_route_input_rcu()
> ip_route_input_noref()
> ip_route_input()
A few other functions are excluded, so that the ip input path coverage
is not completed - i.e. ip_route_use_hint(), is that intentional?
In any case does not apply cleanly anymore.
Please answer to the above question and question on patch 1 before
submitting a new revision. At very least the new revision should include
a comment explaining the reasoning for the current choice.
Please, include in each patch the detailed changelog after the '---'
separator.
Thanks,
Paolo
next prev parent reply other threads:[~2024-10-10 8:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 7:46 Menglong Dong
2024-10-07 7:46 ` [PATCH net-next v2 1/7] net: ip: make fib_validate_source() return drop reason Menglong Dong
2024-10-10 8:25 ` Paolo Abeni
2024-10-10 9:18 ` Menglong Dong
2024-10-11 6:42 ` Menglong Dong
2024-10-11 8:49 ` Paolo Abeni
2024-10-11 9:17 ` Menglong Dong
2024-10-07 7:46 ` [PATCH net-next v2 2/7] net: ip: make ip_route_input_mc() " Menglong Dong
2024-10-07 7:46 ` [PATCH net-next v2 3/7] net: ip: make ip_mc_validate_source() " Menglong Dong
2024-10-07 7:46 ` [PATCH net-next v2 4/7] net: ip: make ip_route_input_slow() return drop reasons Menglong Dong
2024-10-07 7:47 ` [PATCH net-next v2 5/7] net: ip: make ip_route_input_rcu() " Menglong Dong
2024-10-07 7:47 ` [PATCH net-next v2 6/7] net: ip: make ip_route_input_noref() " Menglong Dong
2024-10-07 7:47 ` [PATCH net-next v2 7/7] net: ip: make ip_route_input() " Menglong Dong
2024-10-10 8:30 ` Paolo Abeni [this message]
2024-10-10 10:32 ` [PATCH net-next v2 0/7] net: ip: add drop reasons to input route Menglong Dong
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=3c2ad895-3546-4269-8e6d-6f187035f4b5@redhat.com \
--to=pabeni@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dongml2@chinatelecom.cn \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menglong8.dong@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=toke@redhat.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 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®