netdev - [RFC] ethtool: raw packet filtering

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

Message-ID: <459ef75b-69dc-4baa-b7e4-6393b0b358ce@intel.com>
Date: Tue, 5 Dec 2023 11:23:34 -0700
From: Ahmed Zaki <ahmed.zaki@...el.com>
To: <netdev@...r.kernel.org>
CC: <davem@...emloft.net>, <edumazet@...gle.com>, Jakub Kicinski
	<kuba@...nel.org>, <pabeni@...hat.com>, <mkubecek@...e.cz>, "Chittim, Madhu"
	<madhu.chittim@...el.com>, "Samudrala, Sridhar" <sridhar.samudrala@...el.com>
Subject: [RFC] ethtool: raw packet filtering

Hello,

We are planning to send a patch series that enables raw packet filtering 
for ice and iavf. However, ethtool currently allows raw filtering on 
only 8 bytes via "user-def":

   # ethtool -N eth0 flow-type user-def N [m N] action N

We are seeking the community's opinion on how to extend the ntuple 
interface to allow for up to 512 bytes of raw packet filtering. The 
direct approach is:

   # ethtool -N eth0 flow-type raw-fltr N [m N] action N

where N would be allowed to be 512 bytes. Would that be acceptable? Any 
concerns regarding netlink or other user-space/kernel comm?

Thank you.