1. 26 6月, 2020 1 次提交
  2. 03 6月, 2020 1 次提交
  3. 05 5月, 2020 3 次提交
  4. 17 3月, 2020 2 次提交
    • D
      rpc: avoid name lookup when dispatching node device APIs · 69eee587
      Daniel P. Berrangé 提交于
      The node device APIs are a little unusual because we don't use a
      "remote_nonnull_node_device" object on the wire, instead we just
      have a "remote_string" for the device name. This meant dispatcher
      code generation needed special cases. In doing so we mistakenly
      used the virNodeDeviceLookupByName() API which gets dispatched
      into the driver, instead of get_nonnull_node_device() which
      directly populates a virNodeDevicePtr object.
      
      This wasn't a problem with monolithic libvirtd, as the
      virNodeDeviceLookupByName() API call was trivially satisfied
      by the registered driver, albeit with an extra (undesirable)
      authentication check. With the split daemons, the call to
      virNodeDeviceLookupByName() fails in virtqemud, because the
      node device driver obviously doesn't exist in that daemon.
      Reviewed-by: NMichal Privoznik <mprivozn@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      69eee587
    • D
      rpc: fix dispatch for node device APIs for virt drivers · 744208e7
      Daniel P. Berrangé 提交于
      Despite their names, the following APIs:
      
          virNodeDeviceDettach
          virNodeDeviceDetachFlags
          virNodeDeviceReAttach
          virNodeDeviceReset
      
      are all handled by the virt drivers, not the node device driver.
      A bug in the RPC generator meant that these APIs were sent to
      the nodedev driver for handling. This caused breakage with the
      split daemons, since nothing was available to process them.
      Reviewed-by: NMichal Privoznik <mprivozn@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      744208e7
  5. 14 3月, 2020 2 次提交
  6. 09 3月, 2020 1 次提交
  7. 05 3月, 2020 2 次提交
  8. 25 2月, 2020 1 次提交
  9. 07 2月, 2020 2 次提交
  10. 06 2月, 2020 1 次提交
  11. 04 2月, 2020 4 次提交
  12. 30 1月, 2020 1 次提交
  13. 29 1月, 2020 7 次提交
  14. 23 1月, 2020 1 次提交
  15. 17 1月, 2020 1 次提交
  16. 03 1月, 2020 2 次提交
  17. 21 12月, 2019 1 次提交
  18. 20 12月, 2019 5 次提交
  19. 14 12月, 2019 2 次提交