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: <2024121114-subsidize-tattered-dd8c@gregkh>
Date: Wed, 11 Dec 2024 10:18:46 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: jianqi.ren.cn@...driver.com
Cc: cratiu@...dia.com, dtatulea@...dia.com, tariqt@...dia.com,
	pabeni@...hat.com, patches@...ts.linux.dev, stable@...r.kernel.org,
	saeedm@...dia.com, leon@...nel.org, davem@...emloft.net,
	edumazet@...gle.com, kuba@...nel.org, roid@...dia.com,
	netdev@...r.kernel.org, linux-rdma@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 6.1.y] net/mlx5e: Don't call cleanup on profile rollback
 failure

On Wed, Dec 11, 2024 at 06:09:53PM +0800, jianqi.ren.cn@...driver.com wrote:
> From: Cosmin Ratiu <cratiu@...dia.com>
> 
> [ Upstream commit 4dbc1d1a9f39c3711ad2a40addca04d07d9ab5d0 ]

Please note that we can not apply a commit to an older stable tree that
is NOT in newer ones as you would obviously have a regression when
moving to a newer kernel.

I am guessing that you are being tasked with backporting CVE fixes to
older stable kernels, which is great, but please work "down the release
list" by starting with the newest one, and then moving to the older
ones.  Otherwise we just can't take these and you are causing a lot of
extra review/checking time on our side here to verify you are doing it
all correctly :(

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ