[Bug 1961968] Re: Broken network on some AWS instances with focal/impish kernels

2022-03-21 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-105.119

---
linux (5.4.0-105.119) focal; urgency=medium

  * CVE-2022-0847
- lib/iov_iter: initialize "flags" in new pipe_buffer

  * Broken network on some AWS instances with focal/impish kernels
(LP: #1961968)
- SAUCE: Revert "PCI/MSI: Mask MSI-X vectors only on success"

  * [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7
(LP: #1960182)
- s390/cpumf: Support for CPU Measurement Facility CSVN 7
- s390/cpumf: Support for CPU Measurement Sampling Facility LS bit

  * Hipersocket page allocation failure on Ubuntu 20.04 based SSC environments
(LP: #1959529)
- s390/qeth: use memory reserves to back RX buffers

  * CVE-2022-0516
- KVM: s390: Return error on SIDA memop on normal guest

  * CVE-2022-0435
- tipc: improve size validations for received domain records

  * CVE-2022-0492
- cgroup-v1: Require capabilities to set release_agent

  * Recalled NFSv4 files delegations overwhelm server (LP: #1957986)
- NFSv4: Fix delegation handling in update_open_stateid()
- NFSv4: nfs4_callback_getattr() should ignore revoked delegations
- NFSv4: Delegation recalls should not find revoked delegations
- NFSv4: fail nfs4_refresh_delegation_stateid() when the delegation was
  revoked
- NFS: Rename nfs_inode_return_delegation_noreclaim()
- NFSv4: Don't remove the delegation from the super_list more than once
- NFSv4: Hold the delegation spinlock when updating the seqid
- NFSv4: Clear the NFS_DELEGATION_REVOKED flag in
  nfs_update_inplace_delegation()
- NFSv4: Update the stateid seqid in nfs_revoke_delegation()
- NFSv4: Revoke the delegation on success in nfs4_delegreturn_done()
- NFSv4: Ignore requests to return the delegation if it was revoked
- NFSv4: Don't reclaim delegations that have been returned or revoked
- NFSv4: nfs4_return_incompatible_delegation() should check delegation
  validity
- NFSv4: Fix nfs4_inode_make_writeable()
- NFS: nfs_inode_find_state_and_recover() fix stateid matching
- NFSv4: Fix races between open and delegreturn
- NFSv4: Handle NFS4ERR_OLD_STATEID in delegreturn
- NFSv4: Don't retry the GETATTR on old stateid in nfs4_delegreturn_done()
- NFSv4: nfs_inode_evict_delegation() should set NFS_DELEGATION_RETURNING
- NFS: Clear NFS_DELEGATION_RETURN_IF_CLOSED when the delegation is returned
- NFSv4: Try to return the delegation immediately when marked for return on
  close
- NFSv4: Add accounting for the number of active delegations held
- NFSv4: Limit the total number of cached delegations
- NFSv4: Ensure the delegation is pinned in nfs_do_return_delegation()
- NFSv4: Ensure the delegation cred is pinned when we call delegreturn

  * Focal update: v5.4.174 upstream stable release (LP: #1960566)
- HID: uhid: Fix worker destroying device without any protection
- HID: wacom: Reset expected and received contact counts at the same time
- HID: wacom: Ignore the confidence flag when a touch is removed
- HID: wacom: Avoid using stale array indicies to read contact count
- f2fs: fix to do sanity check in is_alive()
- nfc: llcp: fix NULL error pointer dereference on sendmsg() after failed
  bind()
- mtd: rawnand: gpmi: Add ERR007117 protection for nfc_apply_timings
- mtd: rawnand: gpmi: Remove explicit default gpmi clock setting for i.MX6
- x86/gpu: Reserve stolen memory for first integrated Intel GPU
- tools/nolibc: x86-64: Fix startup code bug
- tools/nolibc: i386: fix initial stack alignment
- tools/nolibc: fix incorrect truncation of exit code
- rtc: cmos: take rtc_lock while reading from CMOS
- media: v4l2-ioctl.c: readbuffers depends on V4L2_CAP_READWRITE
- media: flexcop-usb: fix control-message timeouts
- media: mceusb: fix control-message timeouts
- media: em28xx: fix control-message timeouts
- media: cpia2: fix control-message timeouts
- media: s2255: fix control-message timeouts
- media: dib0700: fix undefined behavior in tuner shutdown
- media: redrat3: fix control-message timeouts
- media: pvrusb2: fix control-message timeouts
- media: stk1160: fix control-message timeouts
- can: softing_cs: softingcs_probe(): fix memleak on registration failure
- lkdtm: Fix content of section containing lkdtm_rodata_do_nothing()
- iommu/io-pgtable-arm-v7s: Add error handle for page table allocation 
failure
- dma_fence_array: Fix PENDING_ERROR leak in dma_fence_array_signaled()
- PCI: Add function 1 DMA alias quirk for Marvell 88SE9125 SATA controller
- mm_zone: add function to check if managed dma zone exists
- mm/page_alloc.c: do not warn allocation failure on zone DMA if no managed
  pages
- shmem: fix a race between shmem_unused_huge_shrink and shmem_evict_inode
- drm/rockchip: dsi: Hold pm-runtime across bind/unbind
- 

[Bug 1961968] Re: Broken network on some AWS instances with focal/impish kernels

2022-03-21 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.13.0-37.42

---
linux (5.13.0-37.42) impish; urgency=medium

  * impish/linux: 5.13.0-37.42 -proposed tracker (LP: #1964959)

  * CVE-2022-0742
- ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()

linux (5.13.0-36.41) impish; urgency=medium

  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- debian/dkms-versions -- update from kernel-versions (main/2022.02.21)

  * Broken network on some AWS instances with focal/impish kernels
(LP: #1961968)
- SAUCE: Revert "PCI/MSI: Mask MSI-X vectors only on success"

  * [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is
enabled by IOMMU (LP: #1937295)
- PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled
  by IOMMU

  * [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7
(LP: #1960182)
- s390/cpumf: Support for CPU Measurement Facility CSVN 7
- s390/cpumf: Support for CPU Measurement Sampling Facility LS bit

  * [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call
(LP: #1960875)
- s390/cio: verify the driver availability for path_event call

  * Impish update: upstream stable patchset 2022-02-14 (LP: #1960861)
- devtmpfs regression fix: reconfigure on each mount
- orangefs: Fix the size of a memory allocation in orangefs_bufmap_alloc()
- remoteproc: qcom: pil_info: Don't memcpy_toio more than is provided
- perf: Protect perf_guest_cbs with RCU
- KVM: x86: Register Processor Trace interrupt hook iff PT enabled in guest
- KVM: s390: Clarify SIGP orders versus STOP/RESTART
- 9p: only copy valid iattrs in 9P2000.L setattr implementation
- video: vga16fb: Only probe for EGA and VGA 16 color graphic cards
- media: uvcvideo: fix division by zero at stream start
- rtlwifi: rtl8192cu: Fix WARNING when calling local_irq_restore() with
  interrupts enabled
- firmware: qemu_fw_cfg: fix sysfs information leak
- firmware: qemu_fw_cfg: fix NULL-pointer deref on duplicate entries
- firmware: qemu_fw_cfg: fix kobject leak in probe error path
- KVM: x86: remove PMU FIXED_CTR3 from msrs_to_save_all
- ALSA: hda/realtek: Add speaker fixup for some Yoga 15ITL5 devices
- ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Master after
  reboot from Windows
- ALSA: hda: ALC287: Add Lenovo IdeaPad Slim 9i 14ITL5 speaker quirk
- ALSA: hda/realtek: Add quirk for Legion Y9000X 2020
- ALSA: hda/realtek: Re-order quirk entries for Lenovo
- powerpc/pseries: Get entry and uaccess flush required bits from
  H_GET_CPU_CHARACTERISTICS
- mtd: fixup CFI on ixp4xx
- KVM: x86: don't print when fail to read/write pv eoi memory
- remoteproc: qcom: pas: Add missing power-domain "mxc" for CDSP
- perf annotate: Avoid TUI crash when navigating in the annotation of
  recursive functions
- ALSA: hda/realtek: Use ALC285_FIXUP_HP_GPIO_LED on another HP laptop
- ALSA: hda/tegra: Fix Tegra194 HDA reset failure

  * CVE-2022-0516
- KVM: s390: Return error on SIDA memop on normal guest

  * CVE-2022-0435
- tipc: improve size validations for received domain records

  * CVE-2022-0492
- cgroup-v1: Require capabilities to set release_agent

  * jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >=
11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x (LP: #1954676)
- s390/module: fix loading modules with a lot of relocations

  * Impish update: upstream stable patchset 2022-02-09 (LP: #1960452)
- workqueue: Fix unbind_workers() VS wq_worker_running() race
- Bluetooth: btusb: fix memory leak in btusb_mtk_submit_wmt_recv_urb()
- Bluetooth: btusb: Add two more Bluetooth parts for WCN6855
- Bluetooth: btusb: Add support for Foxconn QCA 0xe0d0
- Bluetooth: bfusb: fix division by zero in send path
- ARM: dts: exynos: Fix BCM4330 Bluetooth reset polarity in I9100
- USB: core: Fix bug in resuming hub's handling of wakeup requests
- USB: Fix "slab-out-of-bounds Write" bug in usb_hcd_poll_rh_status
- ath11k: Fix buffer overflow when scanning with extraie
- mmc: sdhci-pci: Add PCI ID for Intel ADL
- mfd: intel-lpss: Fix too early PM enablement in the ACPI ->probe()
- can: gs_usb: fix use of uninitialized variable, detach device on reception
  of invalid USB data
- can: isotp: convert struct tpcon::{idx,len} to unsigned int
- can: gs_usb: gs_can_start_xmit(): zero-initialize hf->{flags,reserved}
- random: fix data race on crng_node_pool
- random: fix data race on crng init time
- random: fix crash on multiple early calls to add_bootloader_randomness()
- media: Revert "media: uvcvideo: Set unique vdev name based in type"
- staging: wlan-ng: Avoid bitwise vs logical OR warning in
  hfa384x_usb_throttlefn()
- drm/i915: Avoid bitwise vs logical OR warning in 

[Bug 1961968] Re: Broken network on some AWS instances with focal/impish kernels

2022-02-25 Thread Kleber Sacilotto de Souza
Confirmed that impish/linux 5.13.0-32.35 and focal/linux 5.4.0-102.115
are not failing to boot on any AWS instance.

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

** Tags removed: verification-needed-impish
** Tags added: verification-done-impish

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961968

Title:
  Broken network on some AWS instances with focal/impish kernels

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1961968] Re: Broken network on some AWS instances with focal/impish kernels

2022-02-24 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux/5.4.0-102.115 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal' to 'verification-done-focal'. If the problem
still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961968

Title:
  Broken network on some AWS instances with focal/impish kernels

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1961968] Re: Broken network on some AWS instances with focal/impish kernels

2022-02-24 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux/5.13.0-32.35 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-impish

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961968

Title:
  Broken network on some AWS instances with focal/impish kernels

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1961968] Re: Broken network on some AWS instances with focal/impish kernels

2022-02-23 Thread Kleber Sacilotto de Souza
** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Impish)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961968

Title:
  Broken network on some AWS instances with focal/impish kernels

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1961968] Re: Broken network on some AWS instances with focal/impish kernels

2022-02-23 Thread Kleber Sacilotto de Souza
This was already fixed in Jammy/linux by reverting the same patch.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961968

Title:
  Broken network on some AWS instances with focal/impish kernels

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1961968] Re: Broken network on some AWS instances with focal/impish kernels

2022-02-23 Thread Kleber Sacilotto de Souza
SRU requested:
https://lists.ubuntu.com/archives/kernel-team/2022-February/128266.html

** Changed in: linux (Ubuntu Focal)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Impish)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => Critical

** Changed in: linux (Ubuntu Impish)
   Importance: Undecided => Critical

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

** Changed in: linux (Ubuntu Impish)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961968

Title:
  Broken network on some AWS instances with focal/impish kernels

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs