From: "Luck, Tony" <tony.luck@intel.com>
To: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
Cc: Borislav Petkov <bp@alien8.de>,
marmarek@invisiblethingslab.com,
James Morse <james.morse@arm.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Robert Richter <rric@kernel.org>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] EDAC/igen6: Fix NULL pointer dereference
Date: Wed, 18 Jun 2025 08:06:01 -0700 [thread overview]
Message-ID: <aFLV2YMOzXe4iP-I@agluck-desk3> (raw)
In-Reply-To: <20250618031855.1435420-1-qiuxu.zhuo@intel.com>
On Wed, Jun 18, 2025 at 11:18:55AM +0800, Qiuxu Zhuo wrote:
> A kernel panic was reported with the following kernel log:
>
> EDAC igen6: Expected 2 mcs, but only 1 detected.
> BUG: unable to handle page fault for address: 000000000000d570
> ...
> Hardware name: Notebook V54x_6x_TU/V54x_6x_TU, BIOS Dasharo (coreboot+UEFI) v0.9.0 07/17/2024
> RIP: e030:ecclog_handler+0x7e/0xf0 [igen6_edac]
> ...
> igen6_probe+0x2a0/0x343 [igen6_edac]
> ...
> igen6_init+0xc5/0xff0 [igen6_edac]
> ...
>
> This issue occurred because one memory controller was fused off by
Maybe "disabled by BIOS" rather than "fused off by BIOS".
> the BIOS but the igen6_edac driver still checked all the memory
> controllers, including this absent one, to identify the source of
> the error. Accessing the null MMIO for the absent memory controller
> resulted in the oops above.
>
> Fix this issue by reverting the configuration structure to non-const
> and updating the field 'res_cfg->num_imc' to reflect the number of
> detected memory controllers.
>
> Fixes: 20e190b1c1fd ("EDAC/igen6: Skip absent memory controllers")
> Reported-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
> Closes: https://lore.kernel.org/all/aFFN7RlXkaK_loQb@mail-itl/
> Suggested-by: Borislav Petkov <bp@alien8.de>
> Signed-off-by: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
[snip]
> @@ -1350,9 +1350,11 @@ static int igen6_register_mcis(struct pci_dev *pdev, u64 mchbar)
> return -ENODEV;
> }
>
> - if (lmc < res_cfg->num_imc)
> + if (lmc < res_cfg->num_imc) {
> igen6_printk(KERN_WARNING, "Expected %d mcs, but only %d detected.",
> res_cfg->num_imc, lmc);
KERN_WARNING seems overly dramatic. BIOS likely had good reasons to
disable the memory controller (e.g. it isn't connected to any DIMM
slots on the motherboard for this system). So there's nothing actually
wrong that needs to be fixed.
KERN_INFO is enough. Perhaps KERN_DEBUG?
-Tony
next prev parent reply other threads:[~2025-06-18 15:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 11:13 NULL pointer dereference in igen6_probe - 6.16-rc2 Marek Marczykowski-Górecki
2025-06-17 11:57 ` Borislav Petkov
2025-06-17 14:09 ` Zhuo, Qiuxu
2025-06-17 14:51 ` Borislav Petkov
2025-06-17 16:16 ` Zhuo, Qiuxu
2025-06-17 18:20 ` Borislav Petkov
2025-06-18 3:18 ` [PATCH 1/1] EDAC/igen6: Fix NULL pointer dereference Qiuxu Zhuo
2025-06-18 3:26 ` Zhuo, Qiuxu
2025-06-18 13:23 ` marmarek
2025-06-18 13:39 ` Zhuo, Qiuxu
2025-06-18 15:06 ` Luck, Tony [this message]
2025-06-18 15:42 ` Zhuo, Qiuxu
2025-06-18 16:23 ` [PATCH v2 1/2] " Qiuxu Zhuo
2025-06-18 16:23 ` [PATCH v2 2/2] EDAC/igen6: Reduce log level to debug for absent memory controllers Qiuxu Zhuo
2025-06-18 17:46 ` [PATCH v2 1/2] EDAC/igen6: Fix NULL pointer dereference Luck, Tony
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=aFLV2YMOzXe4iP-I@agluck-desk3 \
--to=tony.luck@intel.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marmarek@invisiblethingslab.com \
--cc=mchehab@kernel.org \
--cc=qiuxu.zhuo@intel.com \
--cc=rric@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