1. 14 12月, 2018 1 次提交
    • D
      Remove all Author(s): lines from source file headers · 60046283
      Daniel P. Berrangé 提交于
      In many files there are header comments that contain an Author:
      statement, supposedly reflecting who originally wrote the code.
      In a large collaborative project like libvirt, any non-trivial
      file will have been modified by a large number of different
      contributors. IOW, the Author: comments are quickly out of date,
      omitting people who have made significant contribitions.
      
      In some places Author: lines have been added despite the person
      merely being responsible for creating the file by moving existing
      code out of another file. IOW, the Author: lines give an incorrect
      record of authorship.
      
      With this all in mind, the comments are useless as a means to identify
      who to talk to about code in a particular file. Contributors will always
      be better off using 'git log' and 'git blame' if they need to  find the
      author of a particular bit of code.
      
      This commit thus deletes all Author: comments from the source and adds
      a rule to prevent them reappearing.
      
      The Copyright headers are similarly misleading and inaccurate, however,
      we cannot delete these as they have legal meaning, despite being largely
      inaccurate. In addition only the copyright holder is permitted to change
      their respective copyright statement.
      Reviewed-by: NErik Skultety <eskultet@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      60046283
  2. 20 9月, 2018 2 次提交
  3. 17 9月, 2018 1 次提交
  4. 13 8月, 2018 1 次提交
  5. 26 7月, 2018 1 次提交
  6. 25 7月, 2018 1 次提交
  7. 03 7月, 2018 1 次提交
    • L
      network: properly check for taps that are connected to an OVS bridge · c17edaf7
      Laine Stump 提交于
      When libvirtd is restarted, it checks that each guest tap device is
      still attached to the bridge device that the configuration info says
      it should be connected to. If not, the tap will be disconnected from
      [wherever it is] and connected to [wherever it should be].
      
      The previous code that did this did not account for:
      
      1) the IFLA_MASTER attribute in a netdev's ifinfo will be set to
         "ovs-system" for any tap device connected to an OVS bridge, *not*
         to the name of the bridge it is attached to.
      
      2) virNetDevRemovePort() only works for devices that are attached to a
         standard Linux host bridge. If a device is currently attached to an
         OVS bridge, then virNetDevOpenvswitchRemovePort() must be called
         instead.
      
      This patch remedies those problems, and adds a couple of information
      log messages to aid in debugging any future problem.
      
      Resolves: https://bugzilla.redhat.com/1596176Signed-off-by: NLaine Stump <laine@laine.org>
      ACKed-by: NMichal Privoznik <mprivozn@redhat.com>
      c17edaf7
  8. 12 6月, 2018 1 次提交
  9. 11 5月, 2018 1 次提交
    • J
      util: Clean up consumers of virJSONValueArraySize · 4a3d6ed5
      John Ferlan 提交于
      Rather than have virJSONValueArraySize return a -1 when the input
      is not an array and then splat an error message, let's check for
      an array before calling and then change the return to be a size_t
      instead of ssize_t.
      
      That means using the helper virJSONValueIsArray as well as using a
      more generic error message such as "Malformed <something> array".
      In some cases we can remove stack variables and when we cannot,
      those variables should be size_t not ssize_t. Alter a few references
      of if (!value) to be if (value == 0) instead as well.
      
      Some callers can already assume an array is being worked on based
      on the previous call, so there's less to do.
      Signed-off-by: NJohn Ferlan <jferlan@redhat.com>
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      4a3d6ed5
  10. 04 5月, 2018 1 次提交
  11. 12 4月, 2018 3 次提交
  12. 01 4月, 2018 1 次提交
  13. 06 3月, 2018 1 次提交
  14. 19 2月, 2018 1 次提交
  15. 09 2月, 2018 5 次提交
  16. 01 2月, 2018 2 次提交
  17. 14 12月, 2017 1 次提交
    • P
      conf: Add infrastructure for disk source private data XML · aed3d038
      Peter Krempa 提交于
      VM drivers may need to store additional private data to the status XML
      so that it can be restored after libvirtd restart. Since not everything
      is needed add a callback infrastructure, where VM drivers can add only
      stuff they need.
      
      Note that the private data is formatted as a <privateData> sub-element
      of the <disk> or <backingStore> <source> sub-element. This is done since
      storing it out of band (in the VM private data) would require a complex
      matching process to allow to put the data into correct place.
      aed3d038
  18. 18 10月, 2017 1 次提交
  19. 05 10月, 2017 1 次提交
  20. 17 8月, 2017 13 次提交