mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jeffrey Ji <jeffreyjilinux@gmail.com>
Cc: Eric Dumazet <edumazet@google.com>,
	"David S . Miller" <davem@davemloft.net>,
	Brian Vazquez <brianvv@google.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	jeffreyji <jeffreyji@google.com>
Subject: Re: [PATCH v4 net-next] net-core: add InMacErrors counter
Date: Wed, 26 Jan 2022 18:55:52 -0800	[thread overview]
Message-ID: <20220126185552.57d5b99e@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net> (raw)
In-Reply-To: <20220125232424.2487391-1-jeffreyji@google.com>

On Tue, 25 Jan 2022 23:24:24 +0000 Jeffrey Ji wrote:
> v3-4:
> Remove Change-Id
> 
> v2:
> Use skb_free_reason() for tracing
> Add real-life example in patch msg
> 
> Signed-off-by: jeffreyji <jeffreyji@google.com>
> ---
>  include/linux/skbuff.h    |  1 +
>  include/uapi/linux/snmp.h |  1 +
>  net/ipv4/ip_input.c       |  7 +++++--
>  net/ipv4/proc.c           |  1 +
>  net/ipv6/ip6_input.c      | 12 +++++++-----
>  net/ipv6/proc.c           |  1 +
>  6 files changed, 16 insertions(+), 7 deletions(-)
> 
> diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
> index bf11e1fbd69b..04a36352f677 100644
> --- a/include/linux/skbuff.h
> +++ b/include/linux/skbuff.h
> @@ -320,6 +320,7 @@ enum skb_drop_reason {
>  	SKB_DROP_REASON_TCP_CSUM,
>  	SKB_DROP_REASON_TCP_FILTER,
>  	SKB_DROP_REASON_UDP_CSUM,
> +	SKB_DROP_REASON_BAD_DEST_MAC,

Ah, sorry I missed that you pulled in the reason in v3, I thought you'd
leave it to Menglong. Either way is fine, but "BAD_DEST_MAC" is
probably not the most fortunate name for this reason code.
Menglong had OTHERHOST - that seems more intuitive to me, the MAC
address is not bad, it's just not the address of the local host.

      parent reply	other threads:[~2022-01-27  2:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 23:24 Jeffrey Ji
2022-01-26 17:43 ` Brian Vazquez
2022-01-27  2:55 ` Jakub Kicinski [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=20220126185552.57d5b99e@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net \
    --to=kuba@kernel.org \
    --cc=brianvv@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jeffreyji@google.com \
    --cc=jeffreyjilinux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.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®