[pve-devel] [PATCH manager/storage v4 0/5] fix #4997: lvm, lvm-thin: avoid autoactivating LVs

[Thomas Lamprecht]

Am 08.07.25 um 12:16 schrieb Friedrich Weber:
>> [...] and also because we execute commands even
>> if they are not specified completely but if the user supplied string uniquely
>> matches the start of an existing command, like "u" or "update" in this case
>> here would be enough to trigger the command.
> Right, that might be a bit dangerous. But, thinking about it, even if we
> move the `updatelvm` code to a migration helper script, it could still
> ask the user for confirmation before actually making changes (e.g.
> "Disable autoactivation for all guest volumes in VG 'foo'? [Y/n]").

Yes, that seems sensible for the `-t STDOUT` case, which we normally
use as heuristic to check if it's likely an interactive session.