On Thu, Mar 26, 2026 at 10:19:45AM +0100, Silvan Kaiser wrote: > QEMU currently supports three values for the 'locking' property of > file-based block devices: 'auto' (the default), 'on', and 'off'. > When OFD (Open File Descriptor) locks are available, 'auto' and 'on' > use them; when they are not, 'on' falls back to POSIX locks with a > warning. > > This series adds a fourth value, 'posix', which explicitly forces the > use of traditional POSIX locks (F_SETLK/F_GETLK) regardless of OFD > availability. The motivation is that some userspace filesystem > implementations (e.g. FUSE) handle POSIX locks correctly but do not > fully support OFD lock semantics. Issues with OFD support detection > on underlying file systems and some OFD guarantees not being fully > supported can prohibit users from using the default OFD locking. > Previously, users in this situation had no way to force POSIX locking > without disabling locking entirely.
Don't the OFD locks silently degrade into POSIX lock semantics when used over FUSE ? If not, what is the behaviour problem you're seeing ? With regards, Daniel -- |: https://berrange.com ~~ https://hachyderm.io/@berrange :| |: https://libvirt.org ~~ https://entangle-photo.org :| |: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
