linux-kernel - Re: [PATCH 1/1] mei: vsc: Unregister interrupt handler for system suspend

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]

Date: Wed, 20 Mar 2024 06:45:22 +0000
From: Sakari Ailus <sakari.ailus@...ux.intel.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: stable@...r.kernel.org, linux-kernel@...r.kernel.org,
	Wentong Wu <wentong.wu@...el.com>,
	Dominik Brodowski <linux@...inikbrodowski.net>
Subject: Re: [PATCH 1/1] mei: vsc: Unregister interrupt handler for system
 suspend

On Tue, Mar 19, 2024 at 12:51:34PM +0100, Greg Kroah-Hartman wrote:
> On Tue, Mar 19, 2024 at 10:47:42AM +0000, Sakari Ailus wrote:
> > Hi Greg,
> > 
> > On Tue, Mar 19, 2024 at 08:51:43AM +0100, Greg Kroah-Hartman wrote:
> > > On Mon, Mar 18, 2024 at 10:01:26AM +0200, Sakari Ailus wrote:
> > > > Unregister the MEI VSC interrupt handler before system suspend and
> > > > re-register it at system resume time. This mirrors implementation of other
> > > > MEI devices.
> > > > 
> > > > This patch fixes the bug that causes continuous stream of MEI VSC errors
> > > > after system resume.
> > > > 
> > > > Fixes: 386a766c4169 ("mei: Add MEI hardware support for IVSC device")
> > > > Cc: stable@...r.kernel.org # for 6.8
> > > > Reported-by: Dominik Brodowski <linux@...inikbrodowski.net>
> > > > Signed-off-by: Wentong Wu <wentong.wu@...el.com>
> > > > Signed-off-by: Sakari Ailus <sakari.ailus@...ux.intel.com>
> > > > ---
> > > >  drivers/misc/mei/platform-vsc.c | 17 ++++++-
> > > >  drivers/misc/mei/vsc-tp.c       | 84 +++++++++++++++++++++++----------
> > > >  drivers/misc/mei/vsc-tp.h       |  3 ++
> > > >  3 files changed, 78 insertions(+), 26 deletions(-)
> > > 
> > > What is the git commit id of this in Linus's tree?
> > 
> > This one isn't in Linus's (or any other maintainer) tree yet.
> 
> Then why was it sent only for 6.8?  Please read:
>     https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> for how to do this properly.

Ah, I think I mistakenly included the stable@...r e-mail address in
distribution as the other patch was meant to be sent there. I'll resend
this.

-- 
Sakari Ailus