public inbox for linux-edac@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhiquan Li <zhiquan1.li@intel.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: <linux-edac@vger.kernel.org>
Subject: Re: [bug report] x86/mce: Mark fatal MCE's page as poison to avoid panic in the kdump kernel
Date: Wed, 25 Oct 2023 14:19:26 +0800	[thread overview]
Message-ID: <fe7d6f43-2a10-4c73-be5b-d0702d0d89c8@intel.com> (raw)
In-Reply-To: <12eb6db6-bc24-4e7c-af34-a5c68d49d52a@moroto.mountain>



On 2023/10/25 13:44, Dan Carpenter wrote:
> Hello Zhiquan Li,
> 
> The patch 1d11b153d23b: "x86/mce: Mark fatal MCE's page as poison to
> avoid panic in the kdump kernel" from Oct 23, 2023 (linux-next),
> leads to the following Smatch static checker warning:
> 
> 	arch/x86/kernel/cpu/mce/core.c:299 mce_panic()
> 	error: we previously assumed 'final' could be null (see line 281)
> 
> arch/x86/kernel/cpu/mce/core.c
>     270         /* Now print uncorrected but with the final one last */
>     271         llist_for_each_entry(l, pending, llnode) {
>     272                 struct mce *m = &l->mce;
>     273                 if (!(m->status & MCI_STATUS_UC))
>     274                         continue;
>     275                 if (!final || mce_cmp(m, final)) {
>     276                         print_mce(m);
>     277                         if (!apei_err)
>     278                                 apei_err = apei_write_mce(m);
>     279                 }
>     280         }
>     281         if (final) {
>                     ^^^^^
> This assumes final can be NULL
> 
>     282                 print_mce(final);
>     283                 if (!apei_err)
>     284                         apei_err = apei_write_mce(final);
>     285         }
>     286         if (exp)
>     287                 pr_emerg(HW_ERR "Machine check: %s\n", exp);
>     288         if (!fake_panic) {
>     289                 if (panic_timeout == 0)
>     290                         panic_timeout = mca_cfg.panic_timeout;
>     291 
>     292                 /*
>     293                  * Kdump skips the poisoned page in order to avoid
>     294                  * touching the error bits again. Poison the page even
>     295                  * if the error is fatal and the machine is about to
>     296                  * panic.
>     297                  */
>     298                 if (kexec_crash_loaded()) {
> --> 299                         p = pfn_to_online_page(final->addr >> PAGE_SHIFT);
>                                                        ^^^^^^^^^^^
> Unchecked dereference
> 
>     300                         if (final && (final->status & MCI_STATUS_ADDRV) && p)
>                                     ^^^^^
> Checked too late
> 
>     301                                 SetPageHWPoison(p);

Nice catch!

This part should be changed like these:

+                       if (final && (final->status & MCI_STATUS_ADDRV))
+                               p = pfn_to_online_page(final->addr >> PAGE_SHIFT);
+                               if (p)
+                                       SetPageHWPoison(p);

The assignment can not be put into the "if" condition, checkpatch.pl script
will complain it. So it have to take a separate line.

I'll re-validate the patch and send V5 soon.
Thanks a lot, Dan.

Best Regards,
Zhiquan

>     302                 }
>     303                 panic(msg);
>     304         } else
>     305                 pr_emerg(HW_ERR "Fake kernel panic: %s\n", msg);
>     306 
>     307 out:
>     308         instrumentation_end();
>     309 }
> 
> regards,
> dan carpenter

  reply	other threads:[~2023-10-25  6:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25  5:44 [bug report] x86/mce: Mark fatal MCE's page as poison to avoid panic in the kdump kernel Dan Carpenter
2023-10-25  6:19 ` Zhiquan Li [this message]
2023-10-25  7:48   ` Borislav Petkov

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=fe7d6f43-2a10-4c73-be5b-d0702d0d89c8@intel.com \
    --to=zhiquan1.li@intel.com \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-edac@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox