From: Yazen Ghannam <yazen.ghannam@amd.com>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org,
"Borislav Petkov (AMD)" <bp@alien8.de>,
Tony Luck <tony.luck@intel.com>,
stable@vger.kernel.org, x86@kernel.org
Subject: Re: [tip: ras/urgent] x86/mce: Make sure logged MCEs are processed after sysfs update
Date: Tue, 14 Mar 2023 14:40:32 +0000 [thread overview]
Message-ID: <ZBCHYHq34nlLlXKc@yaz-fattaah> (raw)
In-Reply-To: <167865351393.5837.17719714572303479044.tip-bot2@tip-bot2>
On Sun, Mar 12, 2023 at 08:38:33PM -0000, tip-bot2 for Yazen Ghannam wrote:
> The following commit has been merged into the ras/urgent branch of tip:
>
> Commit-ID: 4783b9cb374af02d49740e00e2da19fd4ed6dec4
> Gitweb: https://git.kernel.org/tip/4783b9cb374af02d49740e00e2da19fd4ed6dec4
> Author: Yazen Ghannam <yazen.ghannam@amd.com>
> AuthorDate: Wed, 01 Mar 2023 22:14:20
> Committer: Borislav Petkov (AMD) <bp@alien8.de>
> CommitterDate: Sun, 12 Mar 2023 21:12:21 +01:00
>
> x86/mce: Make sure logged MCEs are processed after sysfs update
>
> A recent change introduced a flag to queue up errors found during
> boot-time polling. These errors will be processed during late init once
> the MCE subsystem is fully set up.
>
> A number of sysfs updates call mce_restart() which goes through a subset
> of the CPU init flow. This includes polling MCA banks and logging any
> errors found. Since the same function is used as boot-time polling,
> errors will be queued. However, the system is now past late init, so the
> errors will remain queued until another error is found and the workqueue
> is triggered.
>
> Call mce_schedule_work() at the end of mce_restart() so that queued
> errors are processed.
>
> Fixes: 3bff147b187d ("x86/mce: Defer processing of early errors")
> Signed-off-by: Yazen Ghannam <yazen.ghannam@amd.com>
> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
> Reviewed-by: Tony Luck <tony.luck@intel.com>
Thank you!
-Yazen
prev parent reply other threads:[~2023-03-14 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 22:14 [PATCH v2] x86/mce: Schedule work after restart from sysfs update Yazen Ghannam
2023-03-01 22:16 ` Luck, Tony
2023-03-01 22:18 ` Slade Watkins
2023-03-12 20:38 ` [tip: ras/urgent] x86/mce: Make sure logged MCEs are processed after " tip-bot2 for Yazen Ghannam
2023-03-14 14:40 ` Yazen Ghannam [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZBCHYHq34nlLlXKc@yaz-fattaah \
--to=yazen.ghannam@amd.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.