From: David Ahern <dsahern@kernel.org>
To: Eric Dumazet <edumazet@google.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 4/4] ipv6: icmp6: add drop reason support to ndisc_rcv()
Date: Fri, 10 Feb 2023 12:27:55 -0700 [thread overview]
Message-ID: <a43a022f-a758-a824-17c6-292e0b10ad3e@kernel.org> (raw)
In-Reply-To: <20230210184708.2172562-5-edumazet@google.com>
On 2/10/23 11:47 AM, Eric Dumazet wrote:
> Creates three new drop reasons:
>
> SKB_DROP_REASON_IPV6_NDISC_FRAG: invalid frag (suppress_frag_ndisc).
>
> SKB_DROP_REASON_IPV6_NDISC_HOP_LIMIT: invalid hop limit.
>
> SKB_DROP_REASON_IPV6_NDISC_BAD_CODE: invalid NDISC icmp6 code.
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> ---
> include/net/dropreason.h | 9 +++++++++
> include/net/ndisc.h | 2 +-
> net/ipv6/icmp.c | 2 +-
> net/ipv6/ndisc.c | 13 +++++++------
> 4 files changed, 18 insertions(+), 8 deletions(-)
>
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2023-02-10 19:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 18:47 [PATCH net-next 0/4] ipv6: more drop reason Eric Dumazet
2023-02-10 18:47 ` [PATCH net-next 1/4] net: dropreason: add SKB_DROP_REASON_IPV6_BAD_EXTHDR Eric Dumazet
2023-02-10 19:24 ` David Ahern
2023-02-10 18:47 ` [PATCH net-next 2/4] net: add pskb_may_pull_reason() helper Eric Dumazet
2023-02-10 19:24 ` David Ahern
2023-02-10 18:47 ` [PATCH net-next 3/4] ipv6: icmp6: add drop reason support to icmpv6_notify() Eric Dumazet
2023-02-10 19:26 ` David Ahern
2023-02-10 18:47 ` [PATCH net-next 4/4] ipv6: icmp6: add drop reason support to ndisc_rcv() Eric Dumazet
2023-02-10 19:27 ` David Ahern [this message]
2023-02-14 4:10 ` [PATCH net-next 0/4] ipv6: more drop reason patchwork-bot+netdevbpf
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=a43a022f-a758-a824-17c6-292e0b10ad3e@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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;
as well as URLs for NNTP newsgroup(s).