[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB6083F02E240B6E8B8CEE1EAFFC569@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Fri, 30 Sep 2022 15:52:38 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Shuai Xue <xueshuai@...ux.alibaba.com>,
"Rafael J. Wysocki" <rafael@...nel.org>,
James Morse <james.morse@....com>,
"baicar@...amperecomputing.com" <baicar@...amperecomputing.com>
CC: Len Brown <lenb@...nel.org>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Jarkko Sakkinen <jarkko@...nel.org>,
HORIGUCHI NAOYA(堀口 直也)
<naoya.horiguchi@....com>,
"linmiaohe@...wei.com" <linmiaohe@...wei.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Stable <stable@...r.kernel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
"cuibixuan@...ux.alibaba.com" <cuibixuan@...ux.alibaba.com>,
"baolin.wang@...ux.alibaba.com" <baolin.wang@...ux.alibaba.com>,
"zhuo.song@...ux.alibaba.com" <zhuo.song@...ux.alibaba.com>
Subject: RE: [PATCH v2] ACPI: APEI: do not add task_work to kernel thread to
avoid memory leak
> Yes, the error is actually handled in workqueue. I think the point is that the
> synchronous exception signaled by synchronous external abort must be handled
> synchronously, otherwise, it will be signaled again.
Ok. Got it now. Thanks.
For Rafael:
Reviewed-by: Tony Luck <tony.luck@...el.com>
-Tony
Powered by blists - more mailing lists