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 1/7] net: ip: make fib_validate_source() return drop reason
Date: Thu, 10 Oct 2024 10:25:51 +0200 [thread overview]
Message-ID: <7caf130c-56f0-4f78-a006-5323e237cef1@redhat.com> (raw)
In-Reply-To: <20241007074702.249543-2-dongml2@chinatelecom.cn>
On 10/7/24 09:46, Menglong Dong wrote:
> In this commit, we make fib_validate_source/__fib_validate_source return
> -reason instead of errno on error. As the return value of them can be
> -errno, 0, and 1, we can't make it return enum skb_drop_reason directly.
>
> In the origin logic, if __fib_validate_source() return -EXDEV,
> LINUX_MIB_IPRPFILTER will be counted. And now, we need to adjust it by
> checking "reason == SKB_DROP_REASON_IP_RPFILTER". However, this will take
> effect only after the patch "net: ip: make ip_route_input_noref() return
> drop reasons", as we can't pass the drop reasons from
> fib_validate_source() to ip_rcv_finish_core() in this patch.
>
> We set the errno to -EINVAL when fib_validate_source() is called and the
> validation fails, as the errno can be checked in the caller and now its
> value is -reason, which can lead misunderstand.
>
> Following new drop reasons are added in this patch:
>
> SKB_DROP_REASON_IP_LOCAL_SOURCE
> SKB_DROP_REASON_IP_INVALID_SOURCE
>
> Signed-off-by: Menglong Dong <dongml2@chinatelecom.cn>
Looking at the next patches, I'm under the impression that the overall
code will be simpler if you let __fib_validate_source() return directly
a drop reason, and fib_validate_source(), too. Hard to be sure without
actually do the attempt... did you try such patch by any chance?
Thanks!
Paolo
next prev parent reply other threads:[~2024-10-10 8:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 7:46 [PATCH net-next v2 0/7] net: ip: add drop reasons to input route 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 [this message]
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 ` [PATCH net-next v2 0/7] net: ip: add drop reasons to input route Paolo Abeni
2024-10-10 10:32 ` 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=7caf130c-56f0-4f78-a006-5323e237cef1@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