linux-azure: 4.15.0-1022.22~16.04.1 -proposed tracker

Bug #1787159 reported by Kleber Sacilotto de Souza
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Fix Released
Medium
Unassigned
Automated-testing
Fix Released
Medium
Canonical Kernel Team
Certification-testing
Invalid
Medium
Canonical Hardware Certification
Prepare-package
Fix Released
Medium
Kleber Sacilotto de Souza
Prepare-package-meta
Fix Released
Medium
Kleber Sacilotto de Souza
Prepare-package-signed
Fix Released
Medium
Kleber Sacilotto de Souza
Promote-to-proposed
Fix Released
Medium
Steve Langasek
Promote-to-security
Fix Released
Medium
Łukasz Zemczak
Promote-to-updates
Fix Released
Medium
Łukasz Zemczak
Regression-testing
Fix Released
Medium
Kleber Sacilotto de Souza
Security-signoff
Fix Released
Medium
Steve Beattie
Snap-release-to-beta
Fix Released
Medium
Canonical Kernel Team
Snap-release-to-candidate
Fix Released
Medium
Canonical Kernel Team
Snap-release-to-edge
Fix Released
Medium
Canonical Kernel Team
Snap-release-to-stable
Invalid
Medium
Canonical Kernel Team
Stakeholder-signoff
Fix Released
Medium
Joshua R. Poulson
Upload-to-ppa
Invalid
Medium
Canonical Kernel Team
Verification-testing
Fix Released
Medium
Canonical Kernel Team
linux-azure (Ubuntu)
Invalid
Undecided
Unassigned
Xenial
Fix Released
Medium
Unassigned

Bug Description

This bug is for tracking the <version to be filled> upload package. This bug will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1787149
phase: Released
proposed-announcement-sent: true
proposed-testing-requested: true

tags: added: kernel-release-tracking-bug
tags: added: kernel-release-tracking-bug-live
tags: added: xenial
Changed in linux-azure (Ubuntu Xenial):
status: New → Confirmed
Changed in linux-azure (Ubuntu):
status: New → Invalid
Changed in linux-azure (Ubuntu Xenial):
importance: Undecided → Medium
Changed in kernel-sru-workflow:
status: New → In Progress
importance: Undecided → Medium
tags: added: kernel-sru-cycle-2018.07.30-2
tags: added: kernel-sru-backport-of-1787149
Brad Figg (brad-figg)
description: updated
description: updated
summary: - linux-azure: <version to be filled> -proposed tracker
+ linux-azure: 4.15.0-1022.22~16.04.1 -proposed tracker
Brad Figg (brad-figg)
description: updated
description: updated
Brad Figg (brad-figg)
tags: added: block-proposed-xenial
tags: added: block-proposed
description: updated
Brad Figg (brad-figg)
description: updated
description: updated
Revision history for this message
Kleber Sacilotto de Souza (kleber-souza) wrote :

Regression test CMPL.

Issue to note in x86_64 (azure):
  ebizzy - failed on Standard_A0, passed on the rest
  libhugetlbfs - 1 failed (brk_near_huge, bug 1653597), Killed by signal 1, bad config 3, passed on the rest
  monotonic_time - all two tests (or just tsc test) failed on some instances, passed on the rest
  ubuntu_kvm_unit_tests - test skipped due to no KVM support, vmx_control will crash E4 nodes (bug 1747892)
  ubuntu_ltp_syscalls - inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 1775784)
  ubuntu_lttng_smoke_test - module is now built (bug 1765673 fixed) but it's failing on some instances, needs to be investigate (not a regression though)
  ubuntu_lxc - lxc-test-ubuntu failed (Failed to start networking in ubuntu-cloud container, Failed creating ubuntu-cloud container due to too many open files), passed on the rest
  ubuntu_ramfs_stress - failed on Standard_B1s only
  ubuntu_stress_smoke_test - sysfs caused kernel oopsed on some instances (bug 1757057)
  ubuntu_unionmount_overlayfs_suite - it was running before due to "file unexpectedly on union layer" (bug 1751243). Now it's failing on other testcases, which need to be investigated. Not a regression though.
  ubuntu_zram_smoke_test - zram module was never built (bug 1762756), now failing on some instances which needs to be investigated. Not a regression though.

Skipped / blacklisted:
  * ubuntu_ltp
  * ubuntu_nbd_smoke_test
  * ubuntu_quota_smoke_test
  * ubuntu_ramfs_stress
  * ubuntu_seccomp
  * ubuntu_sysdig_smoke_test

Revision history for this message
Joshua R. Poulson (jrp) wrote :

I am seeing the following as well:

https://github.com/linux-test-project/ltp/blob/3c87ef2961dedb10d1f674c6a530e00dbab8ec1b/testcases/kernel/syscalls/open/open10.c
open10 1 TPASS : Test passed in block0.
open10 2 TPASS : Test passed in block1.
open10 3 TFAIL : open10.c:352: open10.testdir.B.19329/setgid: Incorrect modes, setgid bit not set
open10 4 TFAIL : open10.c:359: Test failed in block2.
open10 5 TPASS : Test passed in block3.
open10 6 TFAIL : open10.c:443: Test failed because of above failures.

https://github.com/linux-test-project/ltp/blob/3c87ef2961dedb10d1f674c6a530e00dbab8ec1b/testcases/kernel/syscalls/creat/creat08.c
creat08 1 TPASS : Test passed in block0.
creat08 2 TPASS : Test passed in block1.
creat08 3 TFAIL : creat08.c:366: testdir.B.15913/setgid: Incorrect modes, setgid bit should be set
creat08 4 TFAIL : creat08.c:374: Test failed in block2.
creat08 5 TPASS : Test passed in block3

Revision history for this message
Marcelo Cerri (mhcerri) wrote :

Hi, Josh.

I wasn't able to reproduce those errors using the ltp commit you have specified or the current master branch.

Can you provide more details about the environment you are running the tests on and the instance type as well?

Revision history for this message
Joshua R. Poulson (jrp) wrote :

We ran the LTP tests on a Standard_D14v2 and these 2 failures only happened on 4.15.0-1022, and they passed o n 4.15.0-1021, 1020, and 1018.

In the dmesg log here's the only thing interesting:

[ 661.232275] EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem
[ 661.257207] EXT4-fs (loop0): mounted filesystem without journal. Opts: (null)
[ 671.225952] EXT4-fs (loop0): re-mounted. Opts: (null)
[ 671.242113] EXT4-fs (loop0): re-mounted. Opts: (null)
[ 676.604207] EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem
[ 676.632372] EXT4-fs (loop0): mounted filesystem without journal. Opts: (null)
[ 676.700511] EXT4-fs (loop0): re-mounted. Opts: (null)
[ 687.302673] show_signal_msg: 3 callbacks suppressed
[ 687.302675] shmat01[20108]: segfault at 7f6e5ebd6000 ip 00000000004030b1 sp 00007fffdd8f2340 error 6 in shmat01[400000+16000]
[ 687.302688] Process 20108(shmat01) has RLIMIT_CORE set to 1
[ 687.302688] Aborting core
[ 696.682827] Adding 65532k swap on ./swapfile01. Priority:-2 extents:1 across:65532k FS

Revision history for this message
Marcelo Cerri (mhcerri) wrote :

I tried to run the tests on a DS14_v2 and those tests are still passing. Is that the same instance type you are using? I couldn't find one named D14_v2.

Previously I was running the individual tests manually but even running the complete test suite, those test cases are still passing.

Is that a VM that you can provide me access to?

Revision history for this message
Joshua R. Poulson (jrp) wrote :

Looks good. LTP errors corrected by updating tests.

Brad Figg (brad-figg)
tags: removed: block-proposed-xenial
tags: removed: block-proposed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (36.0 KiB)

This bug was fixed in the package linux-azure - 4.15.0-1022.22~16.04.1

---------------
linux-azure (4.15.0-1022.22~16.04.1) xenial; urgency=medium

  * linux-azure: 4.15.0-1022.22~16.04.1 -proposed tracker (LP: #1787159)

  * linux-azure: 4.15.0-1022.22 -proposed tracker (LP: #1787155)

  * linux-azure: make sure CONFIG_MLX{4,5}_INFINIBAND stays as "y"
    (LP: #1785822)
    - [Config] azure: Ensure CONFIG_MLX5_INFINIBAND=y

  [ Ubuntu: 4.15.0-33.36 ]

  * linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
  * RTNL assertion failure on ipvlan (LP: #1776927)
    - ipvlan: drop ipv6 dependency
    - ipvlan: use per device spinlock to protect addrs list updates
    - SAUCE: fix warning from "ipvlan: drop ipv6 dependency"
  * ubuntu_bpf_jit test failed on Bionic s390x systems (LP: #1753941)
    - test_bpf: flag tests that cannot be jited on s390
  * HDMI/DP audio can't work on the laptop of Dell Latitude 5495 (LP: #1782689)
    - drm/nouveau: fix nouveau_dsm_get_client_id()'s return type
    - drm/radeon: fix radeon_atpx_get_client_id()'s return type
    - drm/amdgpu: fix amdgpu_atpx_get_client_id()'s return type
    - platform/x86: apple-gmux: fix gmux_get_client_id()'s return type
    - ALSA: hda: use PCI_BASE_CLASS_DISPLAY to replace PCI_CLASS_DISPLAY_VGA
    - vga_switcheroo: set audio client id according to bound GPU id
  * locking sockets broken due to missing AppArmor socket mediation patches
    (LP: #1780227)
    - UBUNTU SAUCE: apparmor: fix apparmor mediating locking non-fs, unix sockets
  * Update2 for ocxl driver (LP: #1781436)
    - ocxl: Fix page fault handler in case of fault on dying process
  * netns: unable to follow an interface that moves to another netns
    (LP: #1774225)
    - net: core: Expose number of link up/down transitions
    - dev: always advertise the new nsid when the netns iface changes
    - dev: advertise the new ifindex when the netns iface changes
  * [Bionic] Disk IO hangs when using BFQ as io scheduler (LP: #1780066)
    - block, bfq: fix occurrences of request finish method's old name
    - block, bfq: remove batches of confusing ifdefs
    - block, bfq: add requeue-request hook
  * HP ProBook 455 G5 needs mute-led-gpio fixup (LP: #1781763)
    - ALSA: hda: add mute led support for HP ProBook 455 G5
  * [Bionic] bug fixes to improve stability of the ThunderX2 i2c driver
    (LP: #1781476)
    - i2c: xlp9xx: Fix issue seen when updating receive length
    - i2c: xlp9xx: Make sure the transfer size is not more than
      I2C_SMBUS_BLOCK_SIZE
  * x86/kvm: fix LAPIC timer drift when guest uses periodic mode (LP: #1778486)
    - x86/kvm: fix LAPIC timer drift when guest uses periodic mode
  * Please include ax88179_178a and r8152 modules in d-i udeb (LP: #1771823)
    - [Config:] d-i: Add ax88179_178a and r8152 to nic-modules
  * Nvidia fails after switching its mode (LP: #1778658)
    - PCI: Restore config space on runtime resume despite being unbound
  * Kernel error "task zfs:pid blocked for more than 120 seconds" (LP: #1781364)
    - SAUCE: (noup) zfs to 0.7.5-1ubuntu16.3
  * CVE-2018-12232
    - PATCH 1/1] socket: close race condition between sock_close() and
      sockfs_setattr()
  * CVE-2018-10323
 ...

Changed in linux-azure (Ubuntu Xenial):
status: Confirmed → Fix Released
Brad Figg (brad-figg)
description: updated
description: updated
Revision history for this message
Brad Figg (brad-figg) wrote : Package Released!

The package has been published and the bug is being set to Fix Released

Changed in kernel-sru-workflow:
status: In Progress → Fix Released
description: updated
description: updated
tags: removed: kernel-release-tracking-bug-live
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.