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] [day] [month] [year] [list]
Message-ID: <7e49472c-4bbc-49fe-92c6-621e4675d882@linux.dev>
Date: Tue, 3 Feb 2026 16:10:04 -0800
From: "Yanjun.Zhu" <yanjun.zhu@...ux.dev>
To: David Matlack <dmatlack@...gle.com>
Cc: Alex Williamson <alex@...zbot.org>,
 Adithya Jayachandran <ajayachandra@...dia.com>,
 Alexander Graf <graf@...zon.com>, Alex Mastro <amastro@...com>,
 Alistair Popple <apopple@...dia.com>,
 Andrew Morton <akpm@...ux-foundation.org>, Ankit Agrawal
 <ankita@...dia.com>, Bjorn Helgaas <bhelgaas@...gle.com>,
 Chris Li <chrisl@...nel.org>, David Rientjes <rientjes@...gle.com>,
 Jacob Pan <jacob.pan@...ux.microsoft.com>, Jason Gunthorpe <jgg@...dia.com>,
 Jason Gunthorpe <jgg@...pe.ca>, Jonathan Corbet <corbet@....net>,
 Josh Hilke <jrhilke@...gle.com>, Kevin Tian <kevin.tian@...el.com>,
 kexec@...ts.infradead.org, kvm@...r.kernel.org,
 Leon Romanovsky <leon@...nel.org>, Leon Romanovsky <leonro@...dia.com>,
 linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-kselftest@...r.kernel.org, linux-mm@...ck.org,
 linux-pci@...r.kernel.org, Lukas Wunner <lukas@...ner.de>,
 Michał Winiarski <michal.winiarski@...el.com>,
 Mike Rapoport <rppt@...nel.org>, Parav Pandit <parav@...dia.com>,
 Pasha Tatashin <pasha.tatashin@...een.com>,
 Pranjal Shrivastava <praan@...gle.com>, Pratyush Yadav
 <pratyush@...nel.org>, Raghavendra Rao Ananta <rananta@...gle.com>,
 Rodrigo Vivi <rodrigo.vivi@...el.com>, Saeed Mahameed <saeedm@...dia.com>,
 Samiullah Khawaja <skhawaja@...gle.com>,
 Shuah Khan <skhan@...uxfoundation.org>,
 Thomas Hellström <thomas.hellstrom@...ux.intel.com>,
 Tomita Moeko <tomitamoeko@...il.com>, Vipin Sharma <vipinsh@...gle.com>,
 Vivek Kasireddy <vivek.kasireddy@...el.com>, William Tu <witu@...dia.com>,
 Yi Liu <yi.l.liu@...el.com>
Subject: Re: [PATCH v2 02/22] PCI: Add API to track PCI devices preserved
 across Live Update


On 2/2/26 10:14 AM, David Matlack wrote:
> On Sat, Jan 31, 2026 at 10:38 PM Zhu Yanjun <yanjun.zhu@...ux.dev> wrote:
>> 在 2026/1/29 13:24, David Matlack 写道:
>>> Add an API to enable the PCI subsystem to track all devices that are
>>> preserved across a Live Update, including both incoming devices (passed
>>> from the previous kernel) and outgoing devices (passed to the next
>>> kernel).
>>>
>>> Use PCI segment number and BDF to keep track of devices across Live
>>> Update. This means the kernel must keep both identifiers constant across
>>> a Live Update for any preserved device. VFs are not supported for now,
>>> since that requires preserving SR-IOV state on the device to ensure the
>>> same number of VFs appear after kexec and with the same BDFs.
>>>
>>> Drivers that preserve devices across Live Update can now register their
>>> struct liveupdate_file_handler with the PCI subsystem so that the PCI
>>> subsystem can allocate and manage File-Lifecycle-Bound (FLB) global data
>>> to track the list of incoming and outgoing preserved devices.
>>>
>>>     pci_liveupdate_register_fh(driver_fh)
>>>     pci_liveupdate_unregister_fh(driver_fh)
>> Can the above 2 functions support the virtual devices? For example,
>> bonding, veth, iSWAP and RXE.
>>
>> These virtual devices do not have BDF. As such, I am not sure if your
>> patches take these virtual devices in to account.
> No this patch series only supports PCI devices, since those are the
> only devices so far we've needed to support.
>
> I am not familiar with any of the devices that you mentioned. If they
> are virtual then does that mean it's all just software? In that case I
> would be curious to know what problem is solved by preserving them in
> the kernel, vs. tearing them down and rebuilding them across a Live
> Udpate.

Bonding, veth, rxe, and siw can be used in KVM environments.

Although these are software-only virtual devices with no associated 
hardware,

they may maintain state that is observable by userspace.

As a result, Live Update should preserve their state across the update.

Zhu Yanjun


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ