This bug was fixed in the package linux-raspi - 5.13.0-1006.7

---------------
linux-raspi (5.13.0-1006.7) impish; urgency=medium

  * impish/linux-raspi: 5.13.0-1006.7 -proposed tracker (LP: #1941058)

  * Miscellaneous Ubuntu changes
    - [Config] update configs with new toolchain versions

linux-raspi (5.13.0-1005.6) impish; urgency=medium

  * impish/linux-raspi: 5.13.0-1005.6 -proposed tracker (LP: #1938560)

  * armhf build failure (LP: #1939308)
    - SAUCE: arm: Fix instruction set selection for GCC 11

  * Packaging resync (LP: #1786013)
    - [Packaging] update variants
    - [Packaging] update update.conf

  * Miscellaneous Ubuntu changes
    - [Packaging] raspi: Initial version of linux-raspi for Impish
    - [Config] raspi: Set RANDOM_TRUST_BOOTLOADER=y

  [ Ubuntu: 5.13.0-14.14 ]

  * impish/linux: 5.13.0-14.14 -proposed tracker (LP: #1938565)
  * Miscellaneous Ubuntu changes
    - SAUCE: Revert "UBUNTU: SAUCE: random: Make getrandom() ready earlier"
    - SAUCE: random: properly make getrandom() ready earlier
  * Miscellaneous upstream changes
    - seq_buf: Fix overflow in seq_buf_putmem_hex()
    - bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc
    - ext4: cleanup in-core orphan list if ext4_truncate() failed to get a
      transaction handle
    - ext4: fix kernel infoleak via ext4_extent_header
    - ext4: fix overflow in ext4_iomap_alloc()
    - ext4: return error code when ext4_fill_flex_info() fails
    - ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit
    - ext4: remove check for zero nr_to_scan in ext4_es_scan()
    - ext4: fix avefreec in find_group_orlov
    - ext4: use ext4_grp_locked_error in mb_find_extent

  [ Ubuntu: 5.13.0-13.13 ]

  * impish/linux: 5.13.0-13.13 -proposed tracker (LP: #1937577)
  * Packaging resync (LP: #1786013)
    - update dkms package versions
  * Miscellaneous Ubuntu changes
    - SAUCE: shifts: update shiftfs for idmapped mounts
    - [Config] re-enable shiftfs
    - [Config] update toolchain in configs

  [ Ubuntu: 5.13.0-12.12 ]

  * Packaging resync (LP: #1786013)
    - update dkms package versions
  * Impish update: v5.13.1 upstream stable release (LP: #1935807)
    - Revert "KVM: x86/mmu: Drop kvm_mmu_extended_role.cr4_la57 hack"
    - Linux 5.13.1
  * ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F
    azure-5.8 (LP: #1927749) // Impish update: v5.13.1 upstream stable release
    (LP: #1935807)
    - selftests/ftrace: fix event-no-pid on 1-core machine
  * ubuntu-host driver lacks lseek ops (LP: #1934110) // Impish update: v5.13.1
    upstream stable release (LP: #1935807)
    - ubuntu-host: add generic lseek op
  * Miscellaneous Ubuntu changes
    - [Config] Enable CONFIG_RANDOMIZE_KSTACK_OFFSET_DEFAULT
    - [Packaging] rename linux-unstable to linux in getabis

 -- Dimitri John Ledkov <dimitri.led...@canonical.com>  Wed, 25 Aug 2021
10:42:56 +0100

** Changed in: linux-raspi (Ubuntu)
       Status: Fix Committed => Fix Released

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

Title:
  HUGETLBFS is disabled

Status in linux-raspi package in Ubuntu:
  Fix Released
Status in linux-raspi-unstable package in Ubuntu:
  Fix Committed
Status in linux-raspi source package in Hirsute:
  Fix Released
Status in linux-raspi-unstable source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  Huge pages can't be managed via hugeadm which requires hugetlbfs.

  [Test Case]

  $ hugeadm --pool-list
  hugeadm:ERROR: kernel does not support huge pages

  With fix:
  $ hugeadm --pool-list
        Size  Minimum  Current  Maximum  Default
       65536        0        0        0
     2097152        0        0        0        *
    33554432        0        0        0
  1073741824        0        0        0

  [Fix]

  Enable CONFIG_HUGETLBFS

  [Regression Potential]

  This config enables code that is disabled by default. However, there
  is minimal stub code running at boot so problems would most likely
  show up as splats during boot or later on when hugetlbfs is explicitly
  mounted by systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1933627/+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