netdev - Re: [PATCH net-next 00/14] devlink: Add support for control packet traps

lists.openwall.net		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 linux-cve-announce 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]

Message-Id: <20200601.114953.415493454319425185.davem@davemloft.net>
Date:   Mon, 01 Jun 2020 11:49:53 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     idosch@...sch.org
Cc:     netdev@...r.kernel.org, kuba@...nel.org, jiri@...lanox.com,
        mlxsw@...lanox.com, idosch@...lanox.com
Subject: Re: [PATCH net-next 00/14] devlink: Add support for control packet
 traps

From: Ido Schimmel <idosch@...sch.org>
Date: Fri, 29 May 2020 21:36:35 +0300

> So far device drivers were only able to register drop and exception
> packet traps with devlink. These traps are used for packets that were
> either dropped by the underlying device or encountered an exception
> (e.g., missing neighbour entry) during forwarding.
> 
> However, in the steady state, the majority of the packets being trapped
> to the CPU are packets that are required for the correct functioning of
> the control plane. For example, ARP request and IGMP query packets.
> 
> This patch set allows device drivers to register such control traps with
> devlink and expose their default control plane policy to user space.
> User space can then tune the packet trap policer settings according to
> its needs, as with existing packet traps.
 ...

Series applied, thank you.