From: Jakub Kicinski <kuba@kernel.org>
To: Jeffrey Ji <jeffreyjilinux@gmail.com>
Cc: "Brian Vazquez" <brianvv@google.com>,
"David S . Miller" <davem@davemloft.net>,
"Paolo Abeni" <pabeni@redhat.com>,
"Hideaki YOSHIFUJI" <yoshfuji@linux-ipv6.org>,
"David Ahern" <dsahern@kernel.org>,
"Eric Dumazet" <edumazet@google.com>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"Menglong Dong" <imagedong@tencent.com>,
"Petr Machata" <petrm@nvidia.com>,
"Kumar Kartikeya Dwivedi" <memxor@gmail.com>,
"Arnd Bergmann" <arnd@arndb.de>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"Jeffrey Ji" <jeffreyji@google.com>
Subject: Re: [PATCH net-next] net-core: rx_otherhost_dropped to core_stats
Date: Wed, 6 Apr 2022 22:31:41 -0700 [thread overview]
Message-ID: <20220406223141.51881854@kernel.org> (raw)
In-Reply-To: <20220406172600.1141083-1-jeffreyjilinux@gmail.com>
On Wed, 6 Apr 2022 17:26:00 +0000 Jeffrey Ji wrote:
> From: Jeffrey Ji <jeffreyji@google.com>
>
> Increment rx_otherhost_dropped counter when packet dropped due to
> mismatched dest MAC addr.
>
> An example when this drop can occur is when manually crafting raw
> packets that will be consumed by a user space application via a tap
> device. For testing purposes local traffic was generated using trafgen
> for the client and netcat to start a server
>
> Tested: Created 2 netns, sent 1 packet using trafgen from 1 to the other
> with "{eth(daddr=$INCORRECT_MAC...}", verified that iproute2 showed the
> counter was incremented. (Also had to modify iproute2 to show the stat,
> additional patch for that coming next.)
>
> Signed-off-by: Jeffrey Ji <jeffreyji@google.com>
Acked-by: Jakub Kicinski <kuba@kernel.org>
next prev parent reply other threads:[~2022-04-07 5:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 17:26 [PATCH net-next] net-core: rx_otherhost_dropped to core_stats Jeffrey Ji
2022-04-07 5:31 ` Jakub Kicinski [this message]
2022-04-07 15:36 ` Brian Vazquez
2022-04-07 15:39 ` Eric Dumazet
2022-04-08 4:00 ` 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=20220406223141.51881854@kernel.org \
--to=kuba@kernel.org \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=brianvv@google.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=imagedong@tencent.com \
--cc=jeffreyji@google.com \
--cc=jeffreyjilinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=toke@redhat.com \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).