1. 30 4月, 2019 2 次提交
  2. 26 4月, 2019 1 次提交
  3. 20 4月, 2019 1 次提交
    • M
      libxlDriverConfigDispose: Free @configBaseDir too · 4f18b2d7
      Michal Privoznik 提交于
      Allocated in libxlDriverConfigNew(), the @configBaseDir is never
      freed.
      
       13 bytes in 1 blocks are definitely lost in loss record 36 of 125
          at 0x483579F: malloc (vg_replace_malloc.c:299)
          by 0x8012469: strdup (strdup.c:42)
          by 0x52926DE: virStrdup (virstring.c:966)
          by 0x11D46B: libxlDriverConfigNew (libxl_conf.c:1749)
          by 0x114D78: testCompareXMLToDomConfig (libxlxml2domconfigtest.c:62)
          by 0x1152A3: testCompareXMLToDomConfigHelper (libxlxml2domconfigtest.c:160)
          by 0x115925: virTestRun (testutils.c:174)
          by 0x1154A4: mymain (libxlxml2domconfigtest.c:216)
          by 0x1179E9: virTestMain (testutils.c:1096)
          by 0x1154FD: main (libxlxml2domconfigtest.c:224)
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      4f18b2d7
  4. 18 4月, 2019 1 次提交
  5. 17 4月, 2019 3 次提交
  6. 16 4月, 2019 3 次提交
  7. 13 4月, 2019 3 次提交
  8. 12 4月, 2019 2 次提交
  9. 10 4月, 2019 3 次提交
  10. 03 4月, 2019 1 次提交
  11. 18 3月, 2019 3 次提交
  12. 14 3月, 2019 2 次提交
  13. 06 3月, 2019 1 次提交
  14. 05 3月, 2019 1 次提交
  15. 20 2月, 2019 1 次提交
    • E
      domain: Fix unknown flags diagnosis in virDomainGetXMLDesc · 27c8fd74
      Eric Blake 提交于
      Many drivers had a comment that they did not validate the incoming
      'flags' to virDomainGetXMLDesc() because they were relying on
      virDomainDefFormat() to do it instead. This used to be the case
      (at least since 461e0f1a and friends in 0.9.4 added unknown flag
      checking in general), but regressed in commit 0ecd6851 (1.2.12),
      when all of the drivers were changed to pass 'flags' through the
      new helper virDomainDefFormatConvertXMLFlags(). Since this helper
      silently ignores unknown flags, we need to implement flag checking
      in each driver instead.
      
      Annoyingly, this means that any new flag values added will silently
      be ignored when targeting an older libvirt, rather than our usual
      practice of loudly diagnosing an unsupported flag.  Add comments
      in domain_conf.[ch] to remind us to be extra vigilant about the
      impact when adding flags (a new flag to add data is safe if the
      older server omitting the requested data doesn't break things in
      the newer client; a new flag to suppress data rather than enhancing
      the existing VIR_DOMAIN_XML_SECURE may form a data leak or even a
      security hole).
      
      In the qemu driver, there are multiple callers all funnelling to
      qemuDomainDefFormatBufInternal(); many of them already validated
      flags (and often only a subset of the full set of possible flags),
      but for ease of maintenance, we can also check flags at the common
      helper function.
      Signed-off-by: NEric Blake <eblake@redhat.com>
      Reviewed-by: NJohn Ferlan <jferlan@redhat.com>
      27c8fd74
  16. 12 2月, 2019 1 次提交
  17. 04 2月, 2019 2 次提交
  18. 31 1月, 2019 1 次提交
  19. 24 1月, 2019 1 次提交
    • J
      libxl: Set current memory value after successful balloon · 11c8aca9
      Jim Fehlig 提交于
      The libxl driver does not set the new memory value in the active domain def
      after a successful balloon. This results in the old memory value in
      <currentMemory>. E.g.
      
      virsh dumpxml test | grep currentMemory
        <currentMemory unit='KiB'>20971520</currentMemory>
      virsh setmem test 16777216 --live
      virsh dumpxml test | grep currentMemory
        <currentMemory unit='KiB'>20971520</currentMemory>
      
      Set the new memory value in active domain def after a successful call to
      libxl_set_memory_target().
      Signed-off-by: NJim Fehlig <jfehlig@suse.com>
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      11c8aca9
  20. 09 1月, 2019 1 次提交
  21. 14 12月, 2018 3 次提交
    • D
      Enforce a standard header file guard symbol name · 568a4172
      Daniel P. Berrangé 提交于
      Require that all headers are guarded by a symbol named
      
        LIBVIRT_$FILENAME
      
      where $FILENAME is the uppercased filename, with all characters
      outside a-z changed into '_'.
      
      Note we do not use a leading __ because that is technically a
      namespace reserved for the toolchain.
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      568a4172
    • D
      Fix many mistakes & inconsistencies in header file layout · 4cfd7090
      Daniel P. Berrangé 提交于
      This introduces a syntax-check script that validates header files use a
      common layout:
      
        /*
         ...copyright header...
         */
        <one blank line>
        #ifndef SYMBOL
        # define SYMBOL
        ....content....
        #endif /* SYMBOL */
      
      For any file ending priv.h, before the #ifndef, we will require a
      guard to prevent bogus imports:
      
        #ifndef SYMBOL_ALLOW
        # error ....
        #endif /* SYMBOL_ALLOW */
        <one blank line>
      
      The many mistakes this script identifies are then fixed.
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      4cfd7090
    • 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
  22. 11 12月, 2018 2 次提交
  23. 07 12月, 2018 1 次提交
    • J
      libxl: support openvswitch interfaces · de09ae2f
      Jim Fehlig 提交于
      It is currently possible to use <interface>s of type openvswitch
      with the libxl driver in a non-standard way, e.g.
      
        <interface type='bridge'>
          <source bridge='ovsbr0'/>
          <mac address='00:16:3e:7a:35:ce'/>
          <script path='vif-openvswitch'/>
        </interface>
      
      This patch adds support for openvswitch <interface>s specified
      in typical libvirt config
      
        <interface type='bridge'>
          <source bridge='ovsbr0'/>
          <mac address='00:16:3e:7a:35:ce'/>
          <virtualport type='openvswitch'/>
        </interface>
      
      VLAN tags and trunking are also supported using the extended
      syntax for specifying an openvswitch bridge in libxl
      
         BRIDGE_NAME[.VLAN][:TRUNK:TRUNK]
      
      See Xen's networking wiki for more details on openvswitch support
      
      https://wiki.xenproject.org/wiki/Xen_Networking#Open_vSwitchSigned-off-by: NJim Fehlig <jfehlig@suse.com>
      ACKed-by: NMichal Privoznik <mprivozn@redhat.com>
      de09ae2f