linux-kernel - Re: [PATCH] mailbox: pcc: Fix can't clear level interrupt of type3 in cornor case

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: <20250302144744.h6ybi4sstxduesvh@bogus>
Date: Sun, 2 Mar 2025 14:47:44 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: "lihuisong (C)" <lihuisong@...wei.com>
Cc: linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
	Sudeep Holla <sudeep.holla@....com>, jassisinghbrar@...il.com,
	liuyonglong@...wei.com
Subject: Re: [PATCH] mailbox: pcc: Fix can't clear level interrupt of type3
 in cornor case

On Sun, Mar 02, 2025 at 03:30:01PM +0800, lihuisong (C) wrote:
>
> 在 2025/3/1 0:32, Sudeep Holla 写道:

[...]

> > This may be correct way of fixing the issue here, but I am questioning the
> > existence of this flag now. I have some rework on this file. I will pick
> This flag is for shared interrupt case on type3. please see:
> 3db174e478cb ("mailbox: pcc: Support shared interrupt for multiple
> subspaces")
>

Yes, I looked at all the history of this patch and I saw I had suggested
it. So it took a while to recall why it is a must. I was reworking some
of the recent change added which I couldn't review and got merged. I was
convinced for a short period this flag is not needed but I was wrong.

I will repost the patch with minor updated to the commit message as part
of my series soon to avoid any conflicts.

--
Regards,
Sudeep