[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220304.122547.1342402483120688005.davem@davemloft.net>
Date: Fri, 04 Mar 2022 12:25:47 +0000 (GMT)
From: David Miller <davem@...emloft.net>
To: dongli.zhang@...cle.com
Cc: netdev@...r.kernel.org, bpf@...r.kernel.org,
linux-kernel@...r.kernel.org, kuba@...nel.org, rostedt@...dmis.org,
mingo@...hat.com, ast@...nel.org, daniel@...earbox.net,
andrii@...nel.org, imagedong@...cent.com,
joao.m.martins@...cle.com, joe.jin@...cle.com, dsahern@...il.com,
edumazet@...gle.com
Subject: Re: [PATCH net-next v5 0/4] tun/tap: use kfree_skb_reason() to
trace dropped skb
From: Dongli Zhang <dongli.zhang@...cle.com>
Date: Thu, 3 Mar 2022 22:33:03 -0800
> The commit c504e5c2f964 ("net: skb: introduce kfree_skb_reason()") has
> introduced the kfree_skb_reason() to help track the reason.
>
> The tun and tap are commonly used as virtio-net/vhost-net backend. This is to
> use kfree_skb_reason() to trace the dropped skb for those two drivers.
This patch series does not apply cleanly against net-next, plewase respin.
Thank you.
Powered by blists - more mailing lists