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

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

Title:
  Focal update: v5.4.107 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification

      Impact:
         The upstream process for stable tree updates is quite similar
         in scope to the Ubuntu SRU process, e.g., each patch has to
         demonstrably fix a bug, and each patch is vetted by upstream
         by originating either directly from a mainline/stable Linux tree or
         a minimally backported form of that patch. The following upstream
         stable patches should be included in the Ubuntu kernel:

         v5.4.107 upstream stable release
         from git://git.kernel.org/

  KVM: arm64: nvhe: Save the SPE context early
  btrfs: scrub: Don't check free space before marking a block group RO
  drm/i915/gvt: Set SNOOP for PAT3 on BXT/APL to workaround GPU BB hang
  drm/i915/gvt: Fix mmio handler break on BXT/APL.
  drm/i915/gvt: Fix virtual display setup for BXT/APL
  drm/i915/gvt: Fix port number for BDW on EDID region setup
  drm/i915/gvt: Fix vfio_edid issue for BXT/APL
  fuse: fix live lock in fuse_iget()
  crypto: x86 - Regularize glue function prototypes
  crypto: aesni - Use TEST %reg,%reg instead of CMP $0,%reg
  crypto: x86/aes-ni-xts - use direct calls to and 4-way stride
  net: dsa: tag_mtk: fix 802.1ad VLAN egress
  net: dsa: b53: Support setting learning on port
  Linux 5.4.107
  UBUNTU: upstream stable to v5.4.107

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to