linux-kernel - Re: [PATCH v2 00/10] LUO: PCI subsystem (phase I)

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <mafs04is1lazi.fsf@kernel.org>
Date: Tue, 14 Oct 2025 18:11:13 +0200
From: Pratyush Yadav <pratyush@...nel.org>
To: Pratyush Yadav <pratyush@...nel.org>
Cc: Jason Miu <jasonmiu@...gle.com>,  Chris Li <chrisl@...nel.org>,  Bjorn
 Helgaas <helgaas@...nel.org>,  Pasha Tatashin <pasha.tatashin@...een.com>,
  Bjorn Helgaas <bhelgaas@...gle.com>,  Greg Kroah-Hartman
 <gregkh@...uxfoundation.org>,  "Rafael J. Wysocki" <rafael@...nel.org>,
  Danilo Krummrich <dakr@...nel.org>,  Len Brown <lenb@...nel.org>,
  linux-kernel@...r.kernel.org,  linux-pci@...r.kernel.org,
  linux-acpi@...r.kernel.org,  David Matlack <dmatlack@...gle.com>,  Pasha
 Tatashin <tatashin@...gle.com>,  Vipin Sharma <vipinsh@...gle.com>,  Saeed
 Mahameed <saeedm@...dia.com>,  Adithya Jayachandran
 <ajayachandra@...dia.com>,  Parav Pandit <parav@...dia.com>,  William Tu
 <witu@...dia.com>,  Mike Rapoport <rppt@...nel.org>,  Jason Gunthorpe
 <jgg@...pe.ca>,  Leon Romanovsky <leon@...nel.org>,  skhawaja@...gle.com
Subject: Re: [PATCH v2 00/10] LUO: PCI subsystem (phase I)

On Mon, Oct 13 2025, Pratyush Yadav wrote:

> On Fri, Oct 10 2025, Jason Miu wrote:
[...]
>> For the folio sanity check with KEXEC_HANDOVER_DEBUG, I can follow
>> that up. Would you tell me what we like to check before reboot, I may
>> have missed some context. Thanks!
>
> The idea is to sanity-check the preserved folios in the kexec-reboot
> flow somewhere. The main check discussed was to make sure the folios are
> of the same order as they were preserved with. This will help catch bugs
> where folios might split after being preserved.
>
> Maybe we can add some more checks too? Like making sure the folios
> aren't freed after they were preserved. But that condition is a bit
> trickier to catch. But at least the former should be simple enough to
> do as a start.

Also perhaps check in kho_preserve_folio() that the preserved folio is
not in scratch memory? This can be a non-debug check as well I suppose,
though looping through all scratch areas every time might end up being
too slow.

-- 
Regards,
Pratyush Yadav