*** This bug is a duplicate of bug 1788351 ***
    https://bugs.launchpad.net/bugs/1788351

** This bug has been marked a duplicate of bug 1788351
   bind03 in ubuntu_ltp_syscalls failed with X/B

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1788350

Title:
  bind03 in ubuntu_ltp_syscalls failed with X/B

Status in linux-kvm package in Ubuntu:
  New

Bug description:
  This is a new test. It has passed on Trusty but failed on X/B

  <<<test_start>>>
  tag=bind03 stime=1534863126
  cmdline="bind03"
  contacts=""
  analysis=exit
  <<<test_output>>>
  tst_test.c:1017: INFO: Timeout per run is 0h 05m 00s
  bind03.c:48: FAIL: expected EINVAL: EADDRINUSE

  Summary:
  passed   0
  failed   1
  skipped  0
  warnings 0
  <<<execution_status>>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<<test_end>>>


  
  From the commit message of this test:
      With 0fb44559ffd6  ("af_unix: move unix_mknod() out of bindlock")
      the behavior of bind() for STREAM UNIX sockets changed in
      case a socket that is already bound is passed to bind() again.

      This testcase fails for the new behavior and passes for the
      old one.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1032-kvm 4.4.0-1032.38
  ProcVersionSignature: User Name 4.4.0-1032.38-kvm 4.4.140
  Uname: Linux 4.4.0-1032-kvm x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Aug 22 07:33:43 2018
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1788350/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to