add launchpad bug reports without comments

1 files changed, 15 insertions, 0 deletions

diff --git a/results/scraper/launchpad-without-comments/1905979 b/results/scraper/launchpad-without-comments/1905979
new file mode 100644
index 00000000..200f790b
--- /dev/null
+++ b/results/scraper/launchpad-without-comments/1905979
@@ -0,0 +1,15 @@
+Check if F_OFD_SETLK is supported may give wrong result
+
+In util/osdep.c there is a function qemu_probe_lock_ops() to check if file locks F_OFD_SETLK and F_OFD_GETLK (of the style "Open file description locks (non-POSIX)") are supported.
+
+This test is done by trying a lock operation on the file /dev/null.
+
+This test can get a wrong result.
+
+The result is (probably) if the operating system *in general* supports these locks. However, it does not guarantee that the file system where the lock is really wanted (for instance, in caller raw_check_lock_bytes() in block/file-posix.c) does support these locks.
+
+(In theory it could even be that /dev/null, being a device special file, does not support the lock type while a plain file would.)
+
+This is in particular relevant for disk images which are stored on a shared file system (my particular use case is the Quobyte file system, which appears not to support these locks).
+
+The code as mentioned above is present in the master branch (I checked commit ea8208249d1082eae0444934efb3b59cd3183f05) but also for example on stable-2.11 commit 0982a56a551556c704dc15752dabf57b4be1c640)
\ No newline at end of file