Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu
切换分支/标签
  1. 19 3月, 2015 1 次提交
    • S
      9pfs: Fix warnings from Sparse · 0289a412
      由 Stefan Weil 提交于 
      Sparse report:

9pfs/virtio-9p.c:1953:9: warning: returning void-valued expression
9pfs/virtio-9p-handle.c:143:5: warning: returning void-valued expression
9pfs/virtio-9p-handle.c:160:5: warning: returning void-valued expression
9pfs/virtio-9p-local.c:384:5: warning: returning void-valued expression
9pfs/virtio-9p-local.c:415:5: warning: returning void-valued expression
9pfs/virtio-9p-proxy.c:672:5: warning: returning void-valued expression
9pfs/virtio-9p-proxy.c:689:5: warning: returning void-valued expression

Cc: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: NAneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: NStefan Weil <sw@weilnetz.de>
Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      0289a412
  3. 19 6月, 2014 1 次提交
  5. 25 4月, 2014 1 次提交
  7. 03 2月, 2014 1 次提交
    • K
      hw/9pfs: fix P9_STATS_GEN handling · f8b7ee38
      由 Kirill A. Shutemov 提交于 
      Currently we fail getattr request altogether if we can't read
P9_STATS_GEN for some reason. It breaks valid use cases:

E.g let's assume we have non-readable directory with execution bit set
on host and we export it to client over 9p On host we can chdir into
directory, but not open directory on read and list content.

But if client will try to call getattr (as part of chdir(2)) for the
directory it will fail with -EACCES. It happens because we try to open
the directory on read to call ioctl(FS_IOC_GETVERSION), it fails and we
return the error code to client.

It's excessive. The solution is to make P9_STATS_GEN failure non-fatal
for getattr request. Just don't set P9_STATS_GEN flag in result mask on
failure.
Signed-off-by: NKirill A. Shutemov <kirill.shutemov@linux.intel.com>
Signed-off-by: NAneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
      f8b7ee38
  9. 28 5月, 2013 1 次提交
  11. 23 4月, 2013 1 次提交
  13. 09 4月, 2013 1 次提交
    • P
      hw: move headers to include/ · 0d09e41a
      由 Paolo Bonzini 提交于 
      Many of these should be cleaned up with proper qdev-/QOM-ification.
Right now there are many catch-all headers in include/hw/ARCH depending
on cpu.h, and this makes it necessary to compile these files per-target.
However, fixing this does not belong in these patches.
Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      0d09e41a
  15. 01 3月, 2013 1 次提交
  17. 06 2月, 2013 1 次提交
  19. 30 1月, 2013 1 次提交
  21. 19 12月, 2012 2 次提交
  23. 05 10月, 2012 1 次提交
  25. 01 8月, 2012 1 次提交
  27. 12 6月, 2012 1 次提交
    • M
      consolidate qemu_iovec_copy() and qemu_iovec_concat() and make them consistent · 1b093c48
      由 Michael Tokarev 提交于 
      qemu_iovec_concat() is currently a wrapper for
qemu_iovec_copy(), use the former (with extra
"0" arg) in a few places where it is used.

Change skip argument of qemu_iovec_copy() from
uint64_t to size_t, since size of qiov itself
is size_t, so there's no way to skip larger
sizes.  Rename it to soffset, to make it clear
that the offset is applied to src.

Also change the only usage of uint64_t in
hw/9pfs/virtio-9p.c, in v9fs_init_qiov_from_pdu() -
all callers of it actually uses size_t too,
not uint64_t.

One added restriction: as for all other iovec-related
functions, soffset must point inside src.

Order of argumens is already good:
 qemu_iovec_memset(QEMUIOVector *qiov, size_t offset,
                   int c, size_t bytes)
vs:
 qemu_iovec_concat(QEMUIOVector *dst,
                   QEMUIOVector *src,
                   size_t soffset, size_t sbytes)
(note soffset is after _src_ not dst, since it applies to src;
for memset it applies to qiov).

Note that in many places where this function is used,
the previous call is qemu_iovec_reset(), which means
many callers actually want copy (replacing dst content),
not concat.  So we may want to add a wrapper like
qemu_iovec_copy() with the same arguments but which
calls qemu_iovec_reset() before _concat().
Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      1b093c48
  29. 24 2月, 2012 1 次提交
  31. 30 1月, 2012 2 次提交
  33. 04 1月, 2012 2 次提交
  35. 21 12月, 2011 3 次提交
  37. 06 12月, 2011 1 次提交
  39. 05 12月, 2011 2 次提交
  41. 22 11月, 2011 1 次提交
  43. 02 11月, 2011 1 次提交
  45. 31 10月, 2011 2 次提交
  47. 30 10月, 2011 1 次提交
  49. 15 10月, 2011 6 次提交
  51. 12 10月, 2011 1 次提交
  53. 23 9月, 2011 2 次提交