lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 15 Jul 2022 19:26:01 -0700 From: Dan Williams <dan.j.williams@...el.com> To: <ira.weiny@...el.com>, Dan Williams <dan.j.williams@...el.com>, "Bjorn Helgaas" <bhelgaas@...gle.com>, Jonathan Cameron <Jonathan.Cameron@...wei.com> CC: Ira Weiny <ira.weiny@...el.com>, Lukas Wunner <lukas@...ner.de>, "Alison Schofield" <alison.schofield@...el.com>, Vishal Verma <vishal.l.verma@...el.com>, Dave Jiang <dave.jiang@...el.com>, Ben Widawsky <bwidawsk@...nel.org>, <linux-kernel@...r.kernel.org>, <linux-cxl@...r.kernel.org>, <linux-pci@...r.kernel.org> Subject: RE: [PATCH V14 7/7] cxl/port: Introduce cxl_cdat_valid() ira.weiny@ wrote: > From: Ira Weiny <ira.weiny@...el.com> > > The CDAT data is protected by a checksum and should be the proper > length. > > Introduce cxl_cdat_valid() to validate the data. While at it check and > store the sequence number. I am going to drop this one. Userspace can determine validity when it parses it. When the kernel grows a CDAT parser it will rely on the standard validation of ACPI-table-like structures from a future __acpi_table_parse_entries() derivative for this purpose.
Powered by blists - more mailing lists