* [PATCH v4 0/2] ACPI: sysfs: Expose BDAT data region
@ 2026-11-09 18:38 Jamie Nguyen
2026-11-09 18:38 ` [PATCH v4 1/2] ACPI: sysfs: Fix data_attr leak when creating a data file fails Jamie Nguyen
2026-11-09 18:38 ` [PATCH v4 2/2] ACPI: sysfs: Expose BDAT data region Jamie Nguyen
0 siblings, 2 replies; 3+ messages in thread
From: Jamie Nguyen @ 2026-11-09 18:38 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Len Brown, Tony Luck, Punit Agrawal, linux-acpi, linux-kernel
The BIOS Data ACPI Table (BDAT) points to a firmware data structure that
carries memory training results and other boot-time data. Patch 2 exposes
that data as /sys/firmware/acpi/tables/data/BDAT, like the existing BERT
and CCEL data files.
Patch 1 fixes a leak in the existing data file code, where data_attr is
not freed if sysfs_create_bin_file() fails. It moves the file creation and
the cleanup into acpi_table_data_init(), and patch 2 builds on that.
Changes in v4:
- Patch 2: before mapping the BDATHEAD header, reject an address where
the header would wrap around the end of the address space, as
acpi_data_show() already does for the data region. Found by Sashiko
on v3 [3].
Changes in v3:
- Rebased onto v7.4-rc1, which includes the two fixes posted during the
v2 review [1][2]. No code changes.
- Dropped the "Assisted-by:" tag as per latest guidelines, though an
LLM was used to write, review, and test this series.
Changes in v2:
- New patch 1, fixing the data_attr leak for BERT and CCEL as well.
- Patch 2: the BDAT callback only checks the table and sets the address
and size of the data, and returns -ENOMEM if mapping the header fails.
v3: https://lore.kernel.org/r/20261109180945.2438349-1-jamien@nvidia.com
v2: https://lore.kernel.org/r/20261012230632.3574987-1-jamien@nvidia.com
v1: https://lore.kernel.org/r/20261009232955.866131-1-jamien@nvidia.com
[1]: https://lore.kernel.org/r/20261013180728.957618-1-jamien@nvidia.com
[2]: https://lore.kernel.org/r/20261013193900.1258808-1-jamien@nvidia.com
[3]: https://sashiko.dev/#/patchset/20261109180945.2438349-1-jamien%40nvidia.com
Tested on an arm64 server (64K pages), with v2:
- The file matches a /dev/mem dump of the data region taken in the same
boot, byte for byte, and decodes with valid CRCs.
- With lockdown=integrity, /dev/mem is refused and the file still reads.
- Malformed BDAT tables loaded via initrd table upgrade (test-only change
adding BDAT to table_sigs[]) are rejected without creating a file: no
"BDATHEAD" signature, size below the header, non-memory address space,
zero address, and a table shorter than struct acpi_table_bdat.
- With a test-only change that makes sysfs_create_bin_file() fail with
-EEXIST for one BDAT table, kmemleak reports its data_attr as leaked
without patch 1, and the data_attr is freed with patch 1 applied.
Tested in QEMU (x86_64), with the same test-only change:
- BDAT tables with address 0xffffffffffffffff or 0xffffffffffffffe0
are rejected without creating a file. With v3, the first of them
faults in memcpy_fromio() at boot.
- A BDAT table pointing at a valid BDATHEAD structure still gets a
data file with the expected contents.
Jamie Nguyen (2):
ACPI: sysfs: Fix data_attr leak when creating a data file fails
ACPI: sysfs: Expose BDAT data region
Documentation/ABI/testing/sysfs-firmware-acpi | 12 +++
drivers/acpi/sysfs.c | 74 ++++++++++++++++---
2 files changed, 76 insertions(+), 10 deletions(-)
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
--
2.43.0
^ permalink raw reply [flat|nested] 3+ messages in thread
* [PATCH v4 1/2] ACPI: sysfs: Fix data_attr leak when creating a data file fails
2026-11-09 18:38 [PATCH v4 0/2] ACPI: sysfs: Expose BDAT data region Jamie Nguyen
@ 2026-11-09 18:38 ` Jamie Nguyen
2026-11-09 18:38 ` [PATCH v4 2/2] ACPI: sysfs: Expose BDAT data region Jamie Nguyen
1 sibling, 0 replies; 3+ messages in thread
From: Jamie Nguyen @ 2026-11-09 18:38 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Len Brown, Tony Luck, Punit Agrawal, linux-acpi, linux-kernel
acpi_table_data_init() allocates the data_attr for a table's data file
and passes it to the table's init callback. The BERT and CCEL callbacks
free data_attr when the table is invalid, but return the result of
sysfs_create_bin_file() directly, so data_attr is leaked if creating the
file fails.
Create the file and free data_attr on failure in acpi_table_data_init()
instead, so that the callbacks only check the table and set the address
and size of the data.
Fixes: 7dae6326ed76 ("ACPI / sysfs: Extend ACPI sysfs to provide access to boot error region")
Signed-off-by: Jamie Nguyen <jamien@nvidia.com>
---
drivers/acpi/sysfs.c | 24 ++++++++++++++----------
1 file changed, 14 insertions(+), 10 deletions(-)
diff --git a/drivers/acpi/sysfs.c b/drivers/acpi/sysfs.c
index a4534b3e3cfbb5b..4182627eeafd2f8 100644
--- a/drivers/acpi/sysfs.c
+++ b/drivers/acpi/sysfs.c
@@ -454,14 +454,13 @@ static int acpi_bert_data_init(void *th, struct acpi_data_attr *data_attr)
struct acpi_table_bert *bert = th;
if (bert->header.length < sizeof(struct acpi_table_bert) ||
- bert->region_length < sizeof(struct acpi_bert_region)) {
- kfree(data_attr);
+ bert->region_length < sizeof(struct acpi_bert_region))
return -EINVAL;
- }
+
data_attr->addr = bert->address;
data_attr->attr.size = bert->region_length;
- return sysfs_create_bin_file(tables_data_kobj, &data_attr->attr);
+ return 0;
}
static int acpi_ccel_data_init(void *th, struct acpi_data_attr *data_attr)
@@ -469,14 +468,13 @@ static int acpi_ccel_data_init(void *th, struct acpi_data_attr *data_attr)
struct acpi_table_ccel *ccel = th;
if (ccel->header.length < sizeof(struct acpi_table_ccel) ||
- !ccel->log_area_start_address || !ccel->log_area_minimum_length) {
- kfree(data_attr);
+ !ccel->log_area_start_address || !ccel->log_area_minimum_length)
return -EINVAL;
- }
+
data_attr->addr = ccel->log_area_start_address;
data_attr->attr.size = ccel->log_area_minimum_length;
- return sysfs_create_bin_file(tables_data_kobj, &data_attr->attr);
+ return 0;
}
static struct acpi_data_obj {
@@ -492,7 +490,7 @@ static struct acpi_data_obj {
static int acpi_table_data_init(struct acpi_table_header *th, struct acpi_table_attr *table_attr)
{
struct acpi_data_attr *data_attr;
- int i;
+ int i, ret;
for (i = 0; i < NUM_ACPI_DATA_OBJS; i++) {
if (ACPI_COMPARE_NAMESEG(th->signature, acpi_data_objs[i].name)) {
@@ -504,7 +502,13 @@ static int acpi_table_data_init(struct acpi_table_header *th, struct acpi_table_
data_attr->attr.attr.mode = 0400;
strscpy(data_attr->filename, table_attr->filename);
data_attr->attr.attr.name = data_attr->filename;
- return acpi_data_objs[i].fn(th, data_attr);
+ ret = acpi_data_objs[i].fn(th, data_attr);
+ if (!ret)
+ ret = sysfs_create_bin_file(tables_data_kobj,
+ &data_attr->attr);
+ if (ret)
+ kfree(data_attr);
+ return ret;
}
}
return 0;
--
2.43.0
^ permalink raw reply [flat|nested] 3+ messages in thread* [PATCH v4 2/2] ACPI: sysfs: Expose BDAT data region
2026-11-09 18:38 [PATCH v4 0/2] ACPI: sysfs: Expose BDAT data region Jamie Nguyen
2026-11-09 18:38 ` [PATCH v4 1/2] ACPI: sysfs: Fix data_attr leak when creating a data file fails Jamie Nguyen
@ 2026-11-09 18:38 ` Jamie Nguyen
1 sibling, 0 replies; 3+ messages in thread
From: Jamie Nguyen @ 2026-11-09 18:38 UTC (permalink / raw)
To: Rafael J. Wysocki
Cc: Len Brown, Tony Luck, Punit Agrawal, linux-acpi, linux-kernel
The BIOS Data ACPI Table (BDAT) points to a firmware data structure that
carries memory training results and other boot-time data. The table is
only a pointer: /sys/firmware/acpi/tables/BDAT holds the ACPI header and
a Generic Address Structure, and the data itself lives in reserved
memory.
Expose the data as /sys/firmware/acpi/tables/data/BDAT, as is already
done for BERT and CCEL. Unlike those tables, BDAT carries no length, so
check the "BDATHEAD" signature at the start of the data structure and
take the size from its BiosDataStructSize field. Reject sizes smaller
than that header, and addresses where the header would wrap around the
end of the address space, which acpi_os_map_iomem() can't handle.
Document the new file in Documentation/ABI.
The BDAT specification is published by the UEFI Forum [1].
Link: https://uefi.org/sites/default/files/resources/BDAT_Spec_v4_0_9%20%282%29.pdf # [1]
Signed-off-by: Jamie Nguyen <jamien@nvidia.com>
---
Documentation/ABI/testing/sysfs-firmware-acpi | 12 +++++
drivers/acpi/sysfs.c | 50 +++++++++++++++++++
2 files changed, 62 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-firmware-acpi b/Documentation/ABI/testing/sysfs-firmware-acpi
index fa33dda331f2440..5fb50a72d468f5c 100644
--- a/Documentation/ABI/testing/sysfs-firmware-acpi
+++ b/Documentation/ABI/testing/sysfs-firmware-acpi
@@ -275,3 +275,15 @@ Description:
remote_region_id: ID associated with access by agents
non-local to this range of addresses.
+
+What: /sys/firmware/acpi/tables/data/BDAT
+Date: October 2026
+Contact: Jamie Nguyen <jamien@nvidia.com>
+Description:
+ The BIOS data structure referenced by the ACPI BDAT (BIOS Data
+ ACPI Table). It starts with a "BDATHEAD" header and holds data
+ published by firmware, such as memory training results. The
+ file size is the structure size given in that header.
+
+ The format is defined by the BDAT Interface Specification,
+ published by the UEFI Forum. The file is readable by root only.
diff --git a/drivers/acpi/sysfs.c b/drivers/acpi/sysfs.c
index 4182627eeafd2f8..49a820b39c2917a 100644
--- a/drivers/acpi/sysfs.c
+++ b/drivers/acpi/sysfs.c
@@ -477,12 +477,62 @@ static int acpi_ccel_data_init(void *th, struct acpi_data_attr *data_attr)
return 0;
}
+/*
+ * The BDAT table only holds the address of the BIOS data structure. Its
+ * size is in the structure's own header ("BDAT Interface Specification"
+ * v4.0, section 4).
+ */
+struct acpi_bdat_data_header {
+ char signature[8]; /* "BDATHEAD" */
+ u32 size; /* whole structure, including this header */
+ u16 crc16;
+ u16 reserved;
+ u16 primary_version;
+ u16 secondary_version;
+ u32 oem_offset;
+ u32 reserved1;
+ u32 reserved2;
+} __packed;
+
+static int acpi_bdat_data_init(void *th, struct acpi_data_attr *data_attr)
+{
+ struct acpi_table_bdat *bdat = th;
+ struct acpi_bdat_data_header hdr;
+ void __iomem *base;
+ u64 end;
+
+ if (bdat->header.length < sizeof(struct acpi_table_bdat) ||
+ bdat->gas.space_id != ACPI_ADR_SPACE_SYSTEM_MEMORY ||
+ !bdat->gas.address)
+ return -EINVAL;
+
+ /* acpi_os_map_iomem() can't handle a range that wraps around */
+ if (check_add_overflow(bdat->gas.address, sizeof(hdr), &end))
+ return -EINVAL;
+
+ base = acpi_os_map_iomem(bdat->gas.address, sizeof(hdr));
+ if (!base)
+ return -ENOMEM;
+ memcpy_fromio(&hdr, base, sizeof(hdr));
+ acpi_os_unmap_iomem(base, sizeof(hdr));
+
+ if (memcmp(hdr.signature, "BDATHEAD", sizeof(hdr.signature)) ||
+ hdr.size < sizeof(hdr))
+ return -EINVAL;
+
+ data_attr->addr = bdat->gas.address;
+ data_attr->attr.size = hdr.size;
+
+ return 0;
+}
+
static struct acpi_data_obj {
char *name;
int (*fn)(void *, struct acpi_data_attr *);
} acpi_data_objs[] = {
{ ACPI_SIG_BERT, acpi_bert_data_init },
{ ACPI_SIG_CCEL, acpi_ccel_data_init },
+ { ACPI_SIG_BDAT, acpi_bdat_data_init },
};
#define NUM_ACPI_DATA_OBJS ARRAY_SIZE(acpi_data_objs)
--
2.43.0
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-11-09 18:38 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-11-09 18:38 [PATCH v4 0/2] ACPI: sysfs: Expose BDAT data region Jamie Nguyen
2026-11-09 18:38 ` [PATCH v4 1/2] ACPI: sysfs: Fix data_attr leak when creating a data file fails Jamie Nguyen
2026-11-09 18:38 ` [PATCH v4 2/2] ACPI: sysfs: Expose BDAT data region Jamie Nguyen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®