netdev - Re: [PATCH iwl-net v2] i40e: Fix handling changed priv flags

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <599eebcb-32db-4035-bd57-93ec723dbd43@intel.com>
Date: Mon, 4 Nov 2024 13:11:07 +0100
From: Przemek Kitszel <przemyslaw.kitszel@...el.com>
To: Peter Große <pegro@...iks.de>
CC: Paul Menzel <pmenzel@...gen.mpg.de>, <intel-wired-lan@...ts.osuosl.org>,
	Tony Nguyen <anthony.l.nguyen@...el.com>, <netdev@...r.kernel.org>, "Sasha
 Levin" <sashal@...nel.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH iwl-net v2] i40e: Fix handling changed priv flags

On 10/31/24 17:11, Peter Große wrote:
> Am Thu, 31 Oct 2024 08:34:36 +0100
> schrieb Przemek Kitszel <przemyslaw.kitszel@...el.com>:
> 
>>>> Fixes: 70756d0a4727 ("i40e: Use DECLARE_BITMAP for flags and
>>>> hw_features fields in i40e_pf")
>>>> Signed-off-by: Peter Große <pegro@...iks.de>
>>
>> Both the code change and the Fixes: tag are correct, thank you!
>> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@...el.com>
> 
> Great to hear :)
> 
> Would this be material for stable?
> 
> I hope to avoid building my own kernel and just use a hwe kernel of Ubuntu.

I believe so. Especially that you have a Fixes: tag, it's easy to tell
if this patch should be backported to given stable tree.
This happens outside of the Intel, after the patch will be eventually
applied to net tree.

There is an option to CC stable directly, or even point out to what
kernels your patch should be backported to. But in easy cases, I like to
keep it "automatic", thanks to Sasha Levin and Greg KH.

Than OS Vendors will get it down from there.

> 
> 
>> BTW, we obey netdev rules on IWL ML - next revision only after 24-48h
>> and send as standalone series (instead of In-reply-to) - no need to
>> repost this time of course
> 
> Sorry, I'm new to submitting patches here.
> 
> Is there anything else I need to do?

for IWL patches: Intel VAL will test it out (will reach to you in case
of any issues), then Tony will bundle it together with other fixes to
send to net (process is the same for next-, with minor details)

so you could just wait for this fix to be backported to stable

> 
> Kind regards
> Peter
>