Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 21 9月, 2016 1 次提交
  3. 17 4月, 2016 2 次提交
  5. 05 2月, 2016 1 次提交
    • P
      all: Clean up includes · d38ea87a
      由 Peter Maydell 提交于 
      Clean up includes so that osdep.h is included first and headers
which it implies are not included manually.

This commit was created with scripts/clean-includes.
Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
Message-id: 1454089805-5470-16-git-send-email-peter.maydell@linaro.org
      d38ea87a
  7. 16 11月, 2015 1 次提交
  9. 22 10月, 2015 1 次提交
  11. 23 1月, 2015 1 次提交
  13. 06 1月, 2015 1 次提交
  15. 12 11月, 2014 1 次提交
    • P
      seccomp: whitelist syscalls fallocate(), fadvise64(), inotify_init1() and inotify_add_watch() · f73adec7
      由 Philipp Gesang 提交于 
      fallocate() is needed for snapshotting. If it isn’t whitelisted

    $ qemu-img create -f qcow2 x.qcow 1G
    Formatting 'x.qcow', fmt=qcow2 size=1073741824 encryption=off cluster_size=65536 lazy_refcounts=off
    $ qemu-kvm -display none -monitor stdio -sandbox on x.qcow
    QEMU 2.1.50 monitor - type 'help' for more information
    (qemu) savevm foo
    (qemu) loadvm foo

will fail, as will subsequent savevm commands on the same image.

fadvise64(), inotify_init1(), inotify_add_watch() are needed by
the SDL display. Without the whitelist entries,

    qemu-kvm -sandbox on

fails immediately.

In my tests fadvise64() is called 50--51 times per VM run. That
number seems independent of the duration of the run. fallocate(),
inotify_init1(), inotify_add_watch() are called once each.
Accordingly, they are added to the whitelist at a very low
priority.
Signed-off-by: NPhilipp Gesang <philipp.gesang@intra2net.com>
Signed-off-by: NEduardo Otubo <eduardo.otubo@profitbricks.com>
      f73adec7
  17. 21 8月, 2014 1 次提交
  19. 26 4月, 2014 2 次提交
    • P
      seccomp: add shmctl(), mlock(), and munlock() to the syscall whitelist · e3f9bb01
      由 Paul Moore 提交于 
      Additional testing reveals that PulseAudio requires shmctl() and the
mlock()/munlock() syscalls on some systems/configurations.  As before,
on systems that do require these syscalls, the problem can be seen with
the following command line:

  # qemu -monitor stdio  -sandbox on \
         -device intel-hda -device hda-duplex
Signed-off-by: NPaul Moore <pmoore@redhat.com>
Signed-off-by: NEduardo Otubo <otubo@linux.vnet.ibm.com>
      e3f9bb01
    • F
      seccomp: add timerfd_create and timerfd_settime to the whitelist · 84397618
      由 Felix Geyer 提交于 
      libusb calls timerfd_create() and timerfd_settime() when it's built with
timerfd support.

Command to reproduce:

       -device usb-host,hostbus=1,hostaddr=3,id=hostdev0

Log messages:

audit(1390730418.924:135): auid=4294967295 uid=121 gid=103 ses=4294967295
                           pid=5232 comm="qemu-system-x86" sig=31 syscall=283
                           compat=0 ip=0x7f2b0f4e96a7 code=0x0
audit(1390733100.580:142): auid=4294967295 uid=121 gid=103 ses=4294967295
                           pid=16909 comm="qemu-system-x86" sig=31 syscall=286
                           compat=0 ip=0x7f03513a06da code=0x0

Reading a few hundred MB from a USB drive on x86_64 shows this syscall distribution.
Therefore the timerfd_settime priority is set to 242.

    calls  syscall
 --------- ----------------
   5303600 write
   2240554 read
   2167030 ppoll
   2134828 ioctl
    704023 timerfd_settime
    689105 poll
     83122 futex
       803 writev
       476 rt_sigprocmask
       287 recvmsg
       178 brk
Signed-off-by: NFelix Geyer <debfx@fobos.de>
Signed-off-by: NEduardo Otubo <otubo@linux.vnet.ibm.com>
      84397618
  21. 20 1月, 2014 2 次提交
    • P
      seccomp: add some basic shared memory syscalls to the whitelist · 918b94e2
      由 Paul Moore 提交于 
      PulseAudio requires the use of shared memory so add shmget(), shmat(),
and shmdt() to the syscall whitelist.

Reported-by: xuhan@redhat.com
Signed-off-by: NPaul Moore <pmoore@redhat.com>
      918b94e2
    • P
      seccomp: add mkdir() and fchmod() to the whitelist · 0c2acb16
      由 Paul Moore 提交于 
      The PulseAudio library attempts to do a mkdir(2) and fchmod(2) on
"/run/user/<UID>/pulse" which is currently blocked by the syscall
filter; this patch adds the two missing syscalls to the whitelist.
You can reproduce this problem with the following command:

 # qemu -monitor stdio -device intel-hda -device hda-duplex

If watched under strace the following syscalls are shown:

 mkdir("/run/user/0/pulse", 0700)
 fchmod(11, 0700) [NOTE: 11 is the fd for /run/user/0/pulse]

Reported-by: xuhan@redhat.com
Signed-off-by: NPaul Moore <pmoore@redhat.com>
      0c2acb16
  23. 21 12月, 2013 1 次提交
  25. 03 12月, 2013 1 次提交
  27. 25 9月, 2013 1 次提交
  29. 30 7月, 2013 2 次提交
  31. 27 7月, 2013 2 次提交
  33. 31 5月, 2013 1 次提交
  35. 19 12月, 2012 1 次提交
  37. 30 11月, 2012 1 次提交
  39. 17 8月, 2012 1 次提交
    • E
      Adding qemu-seccomp.[ch] (v8) · 2f668be7
      由 Eduardo Otubo 提交于 
      Signed-off-by: NEduardo Otubo <otubo@linux.vnet.ibm.com>
Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
---
v1:
 - I added a syscall struct using priority levels as described in the
   libseccomp man page. The priority numbers are based to the frequency
   they appear in a sample strace from a regular qemu guest run under
   libvirt.

   Libseccomp generates linear BPF code to filter system calls, those rules
   are read one after another. The priority system places the most common
   rules first in order to reduce the overhead when processing them.

v1 -> v2:
 - Fixed some style issues
 - Removed code from vl.c and created qemu-seccomp.[ch]
 - Now using ARRAY_SIZE macro
 - Added more syscalls without priority/frequency set yet

v2 -> v3:
 - Adding copyright and license information
 - Replacing seccomp_whitelist_count just by ARRAY_SIZE
 - Adding header protection to qemu-seccomp.h
 - Moving QemuSeccompSyscall definition to qemu-seccomp.c
 - Negative return from seccomp_start is fatal now.
 - Adding open() and execve() to the whitelis

v3 -> v4:
 - Tests revealed a bigger set of syscalls.
 - seccomp_start() now has an argument to set the mode according to the
   configure option trap or kill.

v4 -> v5:
 - Tests on x86_64 required a new specific set of system calls.
 - libseccomp release 1.0.0: part of the API have changed in this last
   release, had to adapt to the new function signatures.
      2f668be7