bionic/linux-azure-4.15: 4.15.0-1090.100 -proposed tracker

Bug #1882740 reported by Kleber Sacilotto de Souza
12
This bug affects 1 person
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
Unassigned
Prepare-package
Fix Released
Medium
Marcelo Cerri
Prepare-package-meta
Fix Released
Medium
Marcelo Cerri
Prepare-package-signed
Fix Released
Medium
Marcelo Cerri
Promote-to-proposed
Fix Released
Medium
Andy Whitcroft
Promote-to-security
New
Medium
Ubuntu Stable Release Updates Team
Promote-to-updates
New
Medium
Ubuntu Stable Release Updates Team
Regression-testing
Fix Released
Medium
Po-Hsu Lin
Security-signoff
Fix Released
Medium
Steve Beattie
Stakeholder-signoff
Confirmed
Medium
linux-azure stakeholder signoff
Verification-testing
Fix Released
Medium
Canonical Kernel Team
linux-azure-4.15 (Ubuntu)
Bionic
Fix Released
Medium
Unassigned

Bug Description

This bug will contain status and test results related to a kernel source (or snap) as stated in the title.

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: 1885044
packages:
  main: linux-azure-4.15
  meta: linux-meta-azure-4.15
  signed: linux-signed-azure-4.15
phase: Ready for Signoff
phase-changed: Wednesday, 24. June 2020 09:09 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason:
  promote-to-updates: 'Holding -- waiting for signoffs: stakeholder-signoff'
  stakeholder-signoff: Stalled -- waiting for signoff
trackers:
  bionic/linux-azure-fips: bug 1882736
  trusty/linux-azure: bug 1882739
  xenial/linux-azure: bug 1882738
variant: debs
versions:
  main: 4.15.0-1090.100
  meta: 4.15.0.1090.61
  signed: 4.15.0-1090.100

tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-2020.06.08-1
description: updated
tags: added: kernel-sru-derivative-of-1882754
Changed in kernel-sru-workflow:
status: New → Confirmed
importance: Undecided → Medium
Changed in linux-azure-4.15 (Ubuntu Bionic):
importance: Undecided → Medium
Changed in kernel-sru-workflow:
status: Confirmed → In Progress
description: updated
description: updated
Marcelo Cerri (mhcerri)
summary: - bionic/linux-azure-4.15: <version to be filled> -proposed tracker
+ bionic/linux-azure-4.15: 4.15.0-1090.100 -proposed tracker
description: updated
description: updated
description: updated
tags: added: block-proposed-bionic
tags: added: block-proposed
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

4.15.0-1090.100 - azure
Regression test CMPL, RTB.

Issue to note in x86_64 (azure):
  ubuntu_bpf - test_map in ubuntu_bpf failed with "Allowed update sockmap 'x:x' not in ESTABLISHED (bug 1839912)
  ubuntu_kernel_selftests - cpu-hotplug on some instances (bug 1814232) raw_skew test in timers bail out on some instances (bug 1882511)
  ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) ept (bug 1824228) memory (bug 1831449) vmx (bug 1821394) vmx_host_state_area (bug 1866585) vmx_intr_window_test (bug 1866586) vmx_nm_test (bug 1866587) vmx_nmi_window_test (bug 1866588) vmx_pending_event_test (bug 1866591) failed on Standard_D16s_v3, Standard_D2_v3, Standard_D2s_v3, Standard_D48_v3, Standard_E2s_v3, Standard_F2s_v2, Standard_F32s_v2
  ubuntu_ltp - proc01 (bug 1829849) cpuset_hotplug (bug 1834006) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) cpuhotplug02 (bug 1836166) cpuhotplug03 (bug 1836167) cpuhotplug04 (bug 1836169) cpuhotplug06 (bug 1836170) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543)
  ubuntu_ltp_syscalls - btrfs fill_fs test in fallocate06 (bug 1866323) fanotify09 case 3 (bug 1876684) getrusage04 (bug 1841425) kill11 (bug 1865965) move_pages12 on some instances(bug 1831043)
  ubunut_qrt_apparmor - timed out on Standard-B1ms (bug 1783922)

tags: added: regression-testing-passed
description: updated
description: updated
description: updated
Revision history for this message
Marcelo Cerri (mhcerri) wrote :

No outstanding issues with ADT.

description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
tags: removed: kernel-sru-derivative-of-1882754
tags: added: kernel-sru-derivative-of-1885044
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (18.2 KiB)

This bug was fixed in the package linux-azure-4.15 - 4.15.0-1091.101

---------------
linux-azure-4.15 (4.15.0-1091.101) bionic; urgency=medium

  * bionic/linux-azure-4.15: 4.15.0-1091.101 -proposed tracker (LP: #1885057)

  * linux-azure: Update SGX version to version LD_1.33 (LP: #1881338)
    - SAUCE: ubuntu/sgx: Add module alias for ACPI device INT0E0C

  [ Ubuntu: 4.15.0-109.110 ]

  * Packaging resync (LP: #1786013)
    - [Packaging] update helper scripts
    - update dkms package versions
  * Build and ship a signed wireguard.ko (LP: #1861284)
    - [Packaging] wireguard -- add support for building signed .ko
  * CVE-2019-16089
    - SAUCE: nbd_genl_status: null check for nla_nest_start
  * CVE-2019-19642
    - kernel/relay.c: handle alloc_percpu returning NULL in relay_open
  * CVE-2019-12380
    - efi/x86/Add missing error handling to old_memmap 1:1 mapping code
  * CVE-2019-19039 // CVE-2019-19377
    - btrfs: sink flush_fn to extent_write_cache_pages
    - btrfs: extent_io: Move the BUG_ON() in flush_write_bio() one level up
    - btrfs: Don't submit any btree write bio if the fs has errors
  * CVE-2019-19036
    - btrfs: volumes: Use more straightforward way to calculate map length
    - btrfs: tree-checker: Try to detect missing INODE_ITEM
    - Btrfs: tree-checker: detect file extent items with overlapping ranges
    - Btrfs: make tree checker detect checksum items with overlapping ranges
    - btrfs: harden agaist duplicate fsid on scanned devices
    - Btrfs: fix missing data checksums after replaying a log tree
    - btrfs: reloc: fix reloc root leak and NULL pointer dereference
    - btrfs: Validate child tree block's level and first key
    - btrfs: Detect unbalanced tree with empty leaf before crashing btree
      operations
  * CVE-2019-19318
    - btrfs: tree-checker: Replace root parameter with fs_info
    - btrfs: tree-checker: Check level for leaves and nodes
    - btrfs: tree-checker: get fs_info from eb in generic_err
    - btrfs: tree-checker: get fs_info from eb in file_extent_err
    - btrfs: tree-checker: get fs_info from eb in check_csum_item
    - btrfs: tree-checker: get fs_info from eb in dir_item_err
    - btrfs: tree-checker: get fs_info from eb in check_dir_item
    - btrfs: tree-checker: get fs_info from eb in block_group_err
    - btrfs: tree-checker: get fs_info from eb in check_block_group_item
    - btrfs: tree-checker: get fs_info from eb in check_extent_data_item
    - btrfs: tree-checker: get fs_info from eb in check_leaf_item
    - btrfs: tree-checker: get fs_info from eb in check_leaf
    - btrfs: tree-checker: get fs_info from eb in chunk_err
    - btrfs: tree-checker: get fs_info from eb in dev_item_err
    - btrfs: tree-checker: get fs_info from eb in check_dev_item
    - btrfs: tree-checker: get fs_info from eb in check_inode_item
    - btrfs: tree-checker: Add ROOT_ITEM check
    - btrfs: tree-checker: Add EXTENT_ITEM and METADATA_ITEM check
    - btrfs: tree-checker: Add simple keyed refs check
    - btrfs: tree-checker: Add EXTENT_DATA_REF check
    - btrfs: tree-checker: Fix wrong check on max devid
    - Btrfs: fix selftests failure due to uninitialized i_mode in test inodes
  * CVE-2...

Changed in linux-azure-4.15 (Ubuntu Bionic):
status: New → Fix Released
Andy Whitcroft (apw)
tags: removed: kernel-release-tracking-bug-live
Changed in kernel-sru-workflow:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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