1. 18 11月, 2013 1 次提交
  2. 11 7月, 2013 1 次提交
  3. 10 7月, 2013 1 次提交
  4. 08 7月, 2013 1 次提交
    • J
      Don't spam logs with "port 0 must be in range" errors · 86dba8f3
      Jiri Denemark 提交于
      Whenever virPortAllocatorRelease is called with port == 0, it complains
      that the port is not in an allowed range, which is expectable as the
      port was never allocated. Let's make virPortAllocatorRelease ignore 0
      ports in a similar way free() ignores NULL pointers.
      86dba8f3
  5. 21 5月, 2013 1 次提交
  6. 18 1月, 2013 2 次提交
    • E
      build: fix build on BSD · f403bdc1
      Eric Blake 提交于
      A build on FreeBSD failed with:
      util/virportallocator.c:108: error: storage size of 'addr' isn't known
      util/virportallocator.c:123: error: 'INADDR_ANY' undeclared (first use in this function)
      
      It turns out that while POSIX allows sockaddr_in to leak in through
      <arpa/inet.h> (the way Linux does it), it is not mandatory, and
      conforming applications are required to get it through <netinet/in.h>.
      
      * src/util/virportallocator.c: Include header for struct
      sockaddr_in.
      * tests/virportallocatortest.c: Likewise.
      f403bdc1
    • D
      Followup fix for integer wraparound in port allocator · 55599102
      Daniel P. Berrange 提交于
      Change iterator variable datatype to int
      55599102
  7. 17 1月, 2013 1 次提交
    • D
      Avoid integer wrap on remotePortMax in QEMU driver · da5a8aee
      Daniel P. Berrange 提交于
      The QEMU driver default max port is 65535, but it then increments
      this by 1 to 65536. This maps to 0 in an unsigned short :-( This
      was apparently done so that for() loops could use "< max" instead
      of "<= max". Remove this insanity and just make the loop do the
      right thing.
      da5a8aee
  8. 16 1月, 2013 1 次提交