netdev - Re: [PATCH net-next v4 0/3] net/sched: Introduce tc block ports tracking and use

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20231006152516.5ff2aeca@kernel.org>
Date: Fri, 6 Oct 2023 15:25:16 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jamal Hadi Salim <jhs@...atatu.com>
Cc: Jiri Pirko <jiri@...nulli.us>, Victor Nogueira <victor@...atatu.com>,
 xiyou.wangcong@...il.com, davem@...emloft.net, pabeni@...hat.com,
 edumazet@...gle.com, mleitner@...hat.com, vladbu@...dia.com,
 simon.horman@...igine.com, pctammela@...atatu.com, netdev@...r.kernel.org,
 kernel@...atatu.com
Subject: Re: [PATCH net-next v4 0/3] net/sched: Introduce tc block ports
 tracking and use

On Fri, 6 Oct 2023 15:06:45 -0400 Jamal Hadi Salim wrote:
> > I don't understand the need for configuration less here. You don't have
> > it for the rest of the actions. Why this is special?  

+1, FWIW

> It is not needed really. Think of an L2 switch - the broadcast action
> is to send to all ports but self.

We do have an implementation of an L2 switch already, what's the use
case which necessitates this new action / functionality?