lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 30 Sep 2020 18:01:50 -0700 (PDT)
From:   David Miller <>
Subject: Re: [PATCH net-next 0/7] drop_monitor: Convert to use devlink

From: Ido Schimmel <>
Date: Tue, 29 Sep 2020 11:15:49 +0300

> From: Ido Schimmel <>
> Drop monitor is able to monitor both software and hardware originated
> drops. Software drops are monitored by having drop monitor register its
> probe on the 'kfree_skb' tracepoint. Hardware originated drops are
> monitored by having devlink call into drop monitor whenever it receives
> a dropped packet from the underlying hardware.
> This patch set converts drop monitor to monitor both software and
> hardware originated drops in the same way - by registering its probe on
> the relevant tracepoint.
> In addition to drop monitor being more consistent, it is now also
> possible to build drop monitor as module instead of as a builtin and
> still monitor hardware originated drops. Initially, CONFIG_NET_DEVLINK
> implied CONFIG_NET_DROP_MONITOR, but after commit def2fbffe62c
> ("kconfig: allow symbols implied by y to become m") we can have
> originated drops will not be monitored.

Series applied, thank you.

Powered by blists - more mailing lists