From: Eric Dumazet <eric.dumazet@gmail.com>
To: izabela.bakollari@gmail.com, nhorman@tuxdriver.com,
davem@davemloft.net, kuba@kernel.org
Cc: netdev@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-kernel-mentees] [PATCH net-next] dropwatch: Support monitoring of dropped frames
Date: Tue, 7 Jul 2020 10:33:50 -0700 [thread overview]
Message-ID: <8aa6bcfe-8117-0fc9-1bc5-9b6a600e0972@gmail.com> (raw)
In-Reply-To: <20200707171515.110818-1-izabela.bakollari@gmail.com>
On 7/7/20 10:15 AM, izabela.bakollari@gmail.com wrote:
> From: Izabela Bakollari <izabela.bakollari@gmail.com>
>
> Dropwatch is a utility that monitors dropped frames by having userspace
> record them over the dropwatch protocol over a file. This augument
> allows live monitoring of dropped frames using tools like tcpdump.
>
> With this feature, dropwatch allows two additional commands (start and
> stop interface) which allows the assignment of a net_device to the
> dropwatch protocol. When assinged, dropwatch will clone dropped frames,
> and receive them on the assigned interface, allowing tools like tcpdump
> to monitor for them.
>
> With this feature, create a dummy ethernet interface (ip link add dev
> dummy0 type dummy), assign it to the dropwatch kernel subsystem, by using
> these new commands, and then monitor dropped frames in real time by
> running tcpdump -i dummy0.
>
> Signed-off-by: Izabela Bakollari <izabela.bakollari@gmail.com>
> ---
> include/uapi/linux/net_dropmon.h | 3 ++
> net/core/drop_monitor.c | 79 +++++++++++++++++++++++++++++++-
> 2 files changed, 80 insertions(+), 2 deletions(-)
>
> diff --git a/include/uapi/linux/net_dropmon.h b/include/uapi/linux/net_dropmon.h
> index 67e31f329190..e8e861e03a8a 100644
> --- a/include/uapi/linux/net_dropmon.h
> +++ b/include/uapi/linux/net_dropmon.h
> @@ -58,6 +58,8 @@ enum {
> NET_DM_CMD_CONFIG_NEW,
> NET_DM_CMD_STATS_GET,
> NET_DM_CMD_STATS_NEW,
> + NET_DM_CMD_START_IFC,
> + NET_DM_CMD_STOP_IFC,
> _NET_DM_CMD_MAX,
> };
>
> @@ -93,6 +95,7 @@ enum net_dm_attr {
> NET_DM_ATTR_SW_DROPS, /* flag */
> NET_DM_ATTR_HW_DROPS, /* flag */
> NET_DM_ATTR_FLOW_ACTION_COOKIE, /* binary */
> + NET_DM_ATTR_IFNAME, /* string */
>
> __NET_DM_ATTR_MAX,
> NET_DM_ATTR_MAX = __NET_DM_ATTR_MAX - 1
> diff --git a/net/core/drop_monitor.c b/net/core/drop_monitor.c
> index 8e33cec9fc4e..8049bff05abd 100644
> --- a/net/core/drop_monitor.c
> +++ b/net/core/drop_monitor.c
> @@ -30,6 +30,7 @@
> #include <net/genetlink.h>
> #include <net/netevent.h>
> #include <net/flow_offload.h>
> +#include <net/sock.h>
>
> #include <trace/events/skb.h>
> #include <trace/events/napi.h>
> @@ -46,6 +47,7 @@
> */
> static int trace_state = TRACE_OFF;
> static bool monitor_hw;
> +struct net_device *interface;
>
> /* net_dm_mutex
> *
> @@ -220,9 +222,8 @@ static void trace_drop_common(struct sk_buff *skb, void *location)
> struct per_cpu_dm_data *data;
> unsigned long flags;
>
> - local_irq_save(flags);
> + spin_lock_irqsave(&data->lock, flags);
> data = this_cpu_ptr(&dm_cpu_data);
> - spin_lock(&data->lock);
This change seems unrelated ?
And also buggy, since data is essentially garbage when you call spin_lock_irqsave(&data->lock, flags);
> dskb = data->skb;
>
> if (!dskb)
> @@ -255,6 +256,12 @@ static void trace_drop_common(struct sk_buff *skb, void *location)
>
> out:
> spin_unlock_irqrestore(&data->lock, flags);
> +
> + if (interface && interface != skb->dev) {
> + skb = skb_clone(skb, GFP_ATOMIC);
skb_clone() can return NULL
> + skb->dev = interface;
> + netif_receive_skb(skb);
> + }
> }
>
> static void trace_kfree_skb_hit(void *ignore, struct sk_buff *skb, void *location)
> @@ -1315,6 +1322,63 @@ static int net_dm_cmd_trace(struct sk_buff *skb,
> return -EOPNOTSUPP;
> }
>
> +static int net_dm_interface_start(struct net *net, const char *ifname)
> +{
> + struct net_device *nd;
> +
> + nd = dev_get_by_name(net, ifname);
> +
> + if (nd) {
> + interface = nd;
> + dev_hold(interface);
> + } else {
> + return -ENODEV;
> + }
> + return 0;
> +}
> +
What happens after this monitoring is started, then the admin does :
rmmod ifb
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-07-07 17:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 17:15 [Linux-kernel-mentees] [PATCH net-next] dropwatch: Support monitoring of dropped frames izabela.bakollari
2020-07-07 17:33 ` Eric Dumazet [this message]
2020-07-07 17:36 ` Eric Dumazet
2020-07-07 17:52 ` Eric Dumazet
2020-07-08 13:54 ` Izabela Bakollari
2020-07-08 14:06 ` Izabela Bakollari
2020-07-07 21:00 ` kernel test robot
2020-07-08 0:27 ` kernel test robot
2020-08-04 16:09 ` [Linux-kernel-mentees] [PATCHv2 " izabela.bakollari
2020-08-04 21:28 ` Cong Wang
2020-08-04 21:58 ` Neil Horman
2020-08-04 23:14 ` David Miller
2020-08-05 10:44 ` Neil Horman
2020-08-10 13:39 ` Izabela Bakollari
2020-08-10 13:56 ` Greg KH
2020-08-31 13:18 ` Michal Schmidt
2020-09-02 16:05 ` Izabela Bakollari
2020-09-02 17:16 ` [Linux-kernel-mentees] [PATCHv3 " izabela.bakollari
2020-09-02 20:35 ` Eric Dumazet
2020-10-23 4:29 ` [Linux-kernel-mentees] [PATCHv4 " izabela.bakollari
2020-10-23 18:20 ` Jakub Kicinski
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=8aa6bcfe-8117-0fc9-1bc5-9b6a600e0972@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=izabela.bakollari@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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).