netdev - Re: [PATCH net-next,v3,1/2] devlink: Add new "max_mac_per

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: <adecffa2-19cd-4630-be0d-8c4b597c8181@redhat.com>
Date: Sun, 7 Sep 2025 12:07:07 +0300
From: mohammad heib <mheib@...hat.com>
To: Simon Horman <horms@...nel.org>
Cc: intel-wired-lan@...ts.osuosl.org, przemyslawx.patynowski@...el.com,
 jiri@...nulli.us, netdev@...r.kernel.org, jacob.e.keller@...el.com,
 aleksandr.loktionov@...el.com, anthony.l.nguyen@...el.com,
 przemyslaw.kitszel@...el.com
Subject: Re: [PATCH net-next,v3,1/2] devlink: Add new "max_mac_per_vf" generic
 device param

Hi Simon,

This patch set targets the iwl tree because the second patch depends on 
changes [1] that are already in the tnguy/net-queue.git tree but have 
not yet reached net/next.

[1] e08bca25bd7f ("i40e: improve VF MAC filters accounting")

Thanks,

On 9/5/25 3:22 PM, Simon Horman wrote:
> On Thu, Sep 04, 2025 at 12:43:04AM +0300, mheib@...hat.com wrote:
>> From: Mohammad Heib <mheib@...hat.com>
>>
>> Add a new device generic parameter to controls the maximum
>> number of MAC filters allowed per VF.
>>
>> For example, to limit a VF to 3 MAC addresses:
>>   $ devlink dev param set pci/0000:3b:00.0 name max_mac_per_vf \
>>          value 3 \
>>          cmode runtime
>>
>> Signed-off-by: Mohammad Heib <mheib@...hat.com>
> 
> Overall this looks good to me, thanks.
> 
> Reviewed-by: Simon Horman <horms@...nel.org>
> 
> One point: This patch-set applies cleanly to iwl but not net-next.
> If it is to be picked up by Tony and go via the iwl tree, then all good
> on my side. But if it is targeted at net-next then you'll need to
> rebase and repost.
> 
> ...
>