qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug 1893010] [NEW] qemu linux-user doesn't support OFD fcntl locks


From: Mike Gelfand
Subject: [Bug 1893010] [NEW] qemu linux-user doesn't support OFD fcntl locks
Date: Wed, 26 Aug 2020 08:36:00 -0000

Public bug reported:

"Open file description locks (non-POSIX)", as they are described in
fcntl(2) man page, aren't supported by qemu-user  and attempting to use
those results in EINVAL. I'm on Gentoo with latest QEMU version
currently available (5.0.0-r2), and trying to emulate ppc64 and s390x on
x86_64.

Looking at linux-user/syscall.c, I'm guessing the issue is in (at least)
`target_to_host_fcntl_cmd` where switch reaches the default clause as
there're no cases for F_OFD_SETLK / F_OFD_SETLKW / F_OFD_GETLK.

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1893010

Title:
  qemu linux-user doesn't support OFD fcntl locks

Status in QEMU:
  New

Bug description:
  "Open file description locks (non-POSIX)", as they are described in
  fcntl(2) man page, aren't supported by qemu-user  and attempting to
  use those results in EINVAL. I'm on Gentoo with latest QEMU version
  currently available (5.0.0-r2), and trying to emulate ppc64 and s390x
  on x86_64.

  Looking at linux-user/syscall.c, I'm guessing the issue is in (at
  least) `target_to_host_fcntl_cmd` where switch reaches the default
  clause as there're no cases for F_OFD_SETLK / F_OFD_SETLKW /
  F_OFD_GETLK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1893010/+subscriptions



reply via email to

[Prev in Thread] Current Thread [Next in Thread]