linux-kernel - Re: [char-misc-next] mei: gsc_proxy: match component when GSC is on different bus

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: <2024021927-study-schilling-9dfa@gregkh>
Date: Mon, 19 Feb 2024 11:40:01 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Tomas Winkler <tomas.winkler@...el.com>
Cc: Alexander Usyskin <alexander.usyskin@...el.com>,
	Vitaly Lubart <vitaly.lubart@...el.com>,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [char-misc-next] mei: gsc_proxy: match component when GSC is on
 different bus

On Sun, Feb 11, 2024 at 03:04:08PM +0200, Tomas Winkler wrote:
> From: Alexander Usyskin <alexander.usyskin@...el.com>
> 
> On Arrow Lake S systems, MEI is no longer strictly connected to bus 0,
> while graphics remain exclusively on bus 0. Adapt the component
> matching logic to accommodate this change:
> 
> Original behavior: Required both MEI and graphics to be on the same
> bus 0.
> 
> New behavior: Only enforces graphics to be on bus 0 (integrated),
> allowing MEI to reside on any bus.
> This ensures compatibility with Arrow Lake S and maintains functionality
> for the legacy systems.
> 
> Cc: <stable@...r.kernel.org>
> Signed-off-by: Alexander Usyskin <alexander.usyskin@...el.com>
> Signed-off-by: Tomas Winkler <tomas.winkler@...el.com>

What commit id does this fix?  How far back in stable kernels should it
go?

thanks,

greg k-h