Thread (92 messages) flat view 92 messages, 6 authors, 2025-11-24

Re: [PATCH v6 02/20] liveupdate: luo_core: integrate with KHO

From: Pasha Tatashin <pasha.tatashin@soleen.com>
Date: 2025-11-18 04:23:32
Also in: linux-doc, linux-fsdevel, linux-mm, lkml

You can avoid that complexity if you register the device with a different
fops, but that's technicality.

Your point about treating the incoming FDT as an underlying resource that
failed to initialize makes sense, but nevertheless userspace needs a
reliable way to detect it and parsing dmesg is not something we should rely
on.
I see two solutions:

1. LUO fails to retrieve the preserved data, the user gets informed by
not finding /dev/liveupdate, and studying the dmesg for what has
happened (in reality in fleets version mismatches should not be
happening, those should be detected in quals).
2. Create a zombie device to return some errno on open, and still
study dmesg to understand what really happened.

I think that 1 is better

Pasha
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help