From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 219495] New: [TPM2] tpm_tis driver crashs during the boot time.
Date: Wed, 13 Nov 2024 02:42:37 +0000 [thread overview]
Message-ID: <bug-219495-215701@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=219495
Bug ID: 219495
Summary: [TPM2] tpm_tis driver crashs during the boot time.
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Platform_x86
Assignee: drivers_platform_x86@kernel-bugs.osdl.org
Reporter: andy.liang@hpe.com
Regression: No
Created attachment 307212
--> https://bugzilla.kernel.org/attachment.cgi?id=307212&action=edit
binary_bios_measurements file
When the TPM2 ACPI table sets the Minimum Log Length size more then 4MB, a call
trace occurs during the boot time. The reason is the kmalloc limits the maximum
size to 4MB for x86 arch.
======
https://elixir.bootlin.com/linux/v6.8/source/arch/x86/include/asm/page_types.h#L10
#define PAGE_SHIFT 12
#define KMALLOC_SHIFT_MAX (MAX_PAGE_ORDER + PAGE_SHIFT)
https://elixir.bootlin.com/linux/v6.8/source/include/linux/mmzone.h#L30
#define MAX_PAGE_ORDER 10
https://elixir.bootlin.com/linux/v6.8/source/include/linux/slab.h#L309
#define KMALLOC_MAX_SIZE (1UL << KMALLOC_SHIFT_MAX)
The max size = (1UL << MAX_PAGE_ORDER + PAGE_SHIFT) = ( 1UL << (10 + 12)) =
2^22 =4,194,304 (4MB)
======
https://elixir.bootlin.com/linux/v6.8/source/drivers/char/tpm/eventlog/acpi.c#L87
[ 11.795176] kernel: __kmalloc+0x2b1/0x330
[ 11.795179] kernel: tpm_read_log_acpi+0x95/0x1e0
Problems:
[ 11.795129] kernel: Call Trace:
[ 11.795131] kernel: <TASK>
[ 11.795133] kernel: ? show_trace_log_lvl+0x1d6/0x2ea
[ 11.795139] kernel: ? show_trace_log_lvl+0x1d6/0x2ea
[ 11.795141] kernel: ? alloc_page_interleave+0x19/0x90
[ 11.795145] kernel: ? show_regs.part.0+0x23/0x29
[ 11.795146] kernel: ? show_regs.cold+0x8/0xd
[ 11.795148] kernel: ? __alloc_pages+0x2b0/0x330
[ 11.795150] kernel: ? __warn+0x8c/0x100
[ 11.795154] kernel: ? __alloc_pages+0x2b0/0x330
[ 11.795156] kernel: ? report_bug+0xa4/0xd0
[ 11.795160] kernel: ? handle_bug+0x39/0x90
[ 11.795162] kernel: ? exc_invalid_op+0x19/0x70
[ 11.795164] kernel: ? asm_exc_invalid_op+0x1b/0x20
[ 11.795167] kernel: ? __alloc_pages+0x2b0/0x330
[ 11.795169] kernel: alloc_page_interleave+0x19/0x90
[ 11.795171] kernel: alloc_pages+0x131/0x1e0
[ 11.795173] kernel: kmalloc_order+0x2f/0xd0
[ 11.795175] kernel: kmalloc_order_trace+0x1d/0x90
[ 11.795176] kernel: __kmalloc+0x2b1/0x330
[ 11.795179] kernel: tpm_read_log_acpi+0x95/0x1e0
[ 11.795183] kernel: tpm_bios_log_setup+0x54/0x270
[ 11.795185] kernel: tpm_chip_register.part.0+0x32/0x1f0
[ 11.795186] kernel: tpm_chip_register+0x61/0xa0
[ 11.795188] kernel: tpm_tis_core_init.cold+0x206/0x448
[ 11.795191] kernel: tpm_tis_init.part.0+0xb4/0x130
[ 11.795193] kernel: tpm_tis_plat_probe+0xd4/0x100
[ 11.795195] kernel: platform_probe+0x46/0xd0
[ 11.795201] kernel: really_probe+0x21f/0x420
[ 11.795203] kernel: __driver_probe_device+0xe8/0x140
[ 11.795205] kernel: driver_probe_device+0x23/0xc0
[ 11.795207] kernel: __driver_attach+0xf7/0x1f0
[ 11.795209] kernel: ? __device_attach_driver+0x140/0x140
[ 11.795211] kernel: bus_for_each_dev+0x7c/0xd0
[ 11.795213] kernel: driver_attach+0x1e/0x30
[ 11.795215] kernel: bus_add_driver+0x148/0x220
[ 11.795217] kernel: driver_register+0x95/0x100
[ 11.795219] kernel: ? tpm_init+0x68/0xfa
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2024-11-13 2:42 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 2:42 bugzilla-daemon [this message]
2024-11-13 5:50 ` [Bug 219495] [TPM2] tpm_tis driver crashs during the boot time bugzilla-daemon
2024-11-13 6:50 ` bugzilla-daemon
2024-11-13 7:05 ` bugzilla-daemon
2024-11-13 7:06 ` bugzilla-daemon
2024-11-13 12:43 ` bugzilla-daemon
2024-11-13 12:47 ` bugzilla-daemon
2024-11-13 13:05 ` bugzilla-daemon
2024-11-13 18:07 ` bugzilla-daemon
2024-11-14 4:48 ` bugzilla-daemon
2024-11-14 4:48 ` bugzilla-daemon
2024-11-18 14:33 ` bugzilla-daemon
2024-11-18 18:57 ` bugzilla-daemon
2024-11-20 7:38 ` bugzilla-daemon
2024-11-20 9:15 ` bugzilla-daemon
2024-12-02 13:48 ` bugzilla-daemon
2024-12-03 6:22 ` bugzilla-daemon
2024-12-03 6:23 ` bugzilla-daemon
2024-12-09 12:56 ` bugzilla-daemon
2024-12-09 14:10 ` bugzilla-daemon
2024-12-11 9:07 ` bugzilla-daemon
2024-12-12 11:38 ` bugzilla-daemon
2024-12-12 11:39 ` bugzilla-daemon
2024-12-12 13:22 ` bugzilla-daemon
2024-12-13 6:22 ` bugzilla-daemon
2024-12-13 6:31 ` bugzilla-daemon
2024-12-13 6:31 ` bugzilla-daemon
2024-12-14 3:28 ` bugzilla-daemon
2024-12-20 1:42 ` bugzilla-daemon
2024-12-20 1:45 ` bugzilla-daemon
2024-12-20 4:09 ` bugzilla-daemon
2024-12-20 14:06 ` bugzilla-daemon
2024-12-20 14:35 ` bugzilla-daemon
2024-12-20 17:50 ` bugzilla-daemon
2024-12-20 18:30 ` bugzilla-daemon
2024-12-20 18:46 ` bugzilla-daemon
2024-12-20 19:14 ` bugzilla-daemon
2024-12-20 19:16 ` bugzilla-daemon
2024-12-20 19:17 ` bugzilla-daemon
2024-12-20 20:16 ` bugzilla-daemon
2024-12-20 20:33 ` bugzilla-daemon
2024-12-20 20:34 ` bugzilla-daemon
2024-12-20 22:48 ` bugzilla-daemon
2024-12-21 0:21 ` bugzilla-daemon
2024-12-21 11:35 ` bugzilla-daemon
2024-12-21 12:46 ` bugzilla-daemon
2024-12-21 14:11 ` bugzilla-daemon
2024-12-21 14:12 ` bugzilla-daemon
2024-12-22 8:34 ` bugzilla-daemon
2024-12-22 15:27 ` bugzilla-daemon
2024-12-22 22:41 ` bugzilla-daemon
2024-12-22 22:55 ` bugzilla-daemon
2024-12-23 7:31 ` bugzilla-daemon
2024-12-23 8:38 ` bugzilla-daemon
2024-12-23 8:40 ` bugzilla-daemon
2024-12-23 8:42 ` bugzilla-daemon
2024-12-23 8:43 ` bugzilla-daemon
2024-12-23 8:43 ` bugzilla-daemon
2024-12-23 8:43 ` bugzilla-daemon
2024-12-23 8:44 ` bugzilla-daemon
2024-12-23 11:05 ` bugzilla-daemon
2024-12-23 11:07 ` bugzilla-daemon
2024-12-23 18:32 ` bugzilla-daemon
2024-12-23 18:34 ` bugzilla-daemon
2024-12-23 18:34 ` bugzilla-daemon
2024-12-24 1:43 ` bugzilla-daemon
2025-01-16 10:53 ` bugzilla-daemon
2025-01-16 11:15 ` bugzilla-daemon
2025-01-16 13:06 ` bugzilla-daemon
2025-01-17 4:14 ` bugzilla-daemon
2025-01-17 4:15 ` bugzilla-daemon
2025-01-17 4:19 ` bugzilla-daemon
2025-01-17 10:02 ` bugzilla-daemon
2025-01-20 4:24 ` bugzilla-daemon
2025-01-20 4:27 ` bugzilla-daemon
2025-01-20 4:29 ` bugzilla-daemon
2025-01-23 14:28 ` bugzilla-daemon
2025-12-22 7:24 ` bugzilla-daemon
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=bug-219495-215701@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@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 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.