btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision

[Matthew Ruffell]

BugLink: https://bugs.launchpad.net/bugs/2004132

[Impact]

xfstests btrfs/154 fails on both Bionic and Focal, leading to a kernel oops and the btrfs volume being forced readonly.

In btrfs, item key collision is allowed for some item types, namely dir item and inode references. When inserting items into the btree, there are two objects, the btrfs_item and the item data. These objects must fit within the btree nodesize.

When a hash collision occurs, and we call btrfs_search_slot() to place the objects in the tree, when btrfs_search_slot() reaches the leaf node, a check is performed to see if we need to split the leaf. The check is incorrect, returning that we need to split the leaf, since it thinks that both btrfs_item and the item data need to be inserted, when in reality, the item can be merged with the existing one and no new btrfs_item will be inserted.

split_leaf() will return EOVERFLOW from following code:

  if (extend && data_size + btrfs_item_size_nr(l, slot) +
      sizeof(struct btrfs_item) > BTRFS_LEAF_DATA_SIZE(fs_info))
      return -EOVERFLOW;

In the rename case, btrfs_check_dir_item_collision() is called early stages of treewalking, and correctly calculates the needed size, taking into account that a hash collision has occurred.

  data_size = sizeof(*di) + name_len;
      if (data_size + btrfs_item_size_nr(leaf, slot) +
          sizeof(struct btrfs_item) > BTRFS_LEAF_DATA_SIZE(root->fs_info))

The two sizes reported from btrfs_check_dir_item_collision() and btrfs_search_slot() are different, and rename fails due to split_leaf() returning -EOVERFLOW, leading to transaction abort and forcing the volume readonly.

Kernel oops:

BTRFS: Transaction aborted (error -75)
WARNING: CPU: 0 PID: 2921 at /build/linux-fTmV3T/linux-4.15.0/fs/btrfs/inode.c:10217 btrfs_rename+0xcf1/0xdf0 [btrfs]
CPU: 0 PID: 2921 Comm: python3 Not tainted 4.15.0-202-generic #213-Ubuntu
RIP: 0010:btrfs_rename+0xcf1/0xdf0 [btrfs]
RSP: 0018:ffff9e6f4183fd20 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff91a493f27b98 RCX: 0000000000000006
RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff91a4bfc1b4d0
RBP: ffff9e6f4183fdc0 R08: 00000000000002b4 R09: 0000000000000004
R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000236
R13: ffff91a493f56518 R14: ffff91a4b6b57b40 R15: ffff91a493f27b98
FS: 00007f6041081740(0000) GS:ffff91a4bfc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6040fe84c8 CR3: 000000015c8ca005 CR4: 0000000000760ef0
PKRU: 55555554
Call Trace:
 btrfs_rename2+0x1d/0x30 [btrfs]
 vfs_rename+0x46e/0x960
 SyS_rename+0x362/0x3c0
 do_syscall_64+0x73/0x130
 entry_SYSCALL_64_after_hwframe+0x41/0xa6
Code: 0f ba a8 d0 cd 00 00 02 72 2b 41 83 f8 fb 0f 84 d9 00 00 00 44 89 c6 48 c7 c7 68 43 4b c0 44 89 55 80 44 89 45 98 e8 8f 5c a6 d0 <0f> 0b 44 8b 45 98 44 8b 55 80 44 89 55 80 44 89 c1 44 89 45 98
---[ end trace 9c6b87a19f4436f3 ]---
BTRFS: error (device vdd) in btrfs_rename:10217: errno=-75 unknown
BTRFS info (device vdd): forced readonly

[Testcase]

Start a fresh Bionic or Focal VM.

Attach two scratch disks, I used standard virtio disks with 3gb of storage each. These disks are /dev/vdc and /dev/vdd.

Compile xfstests:

$ sudo apt-get install acl attr automake bc dbench dump e2fsprogs fio gawk \
        gcc git indent libacl1-dev libaio-dev libcap-dev libgdbm-dev libtool \
        libtool-bin libuuid1 lvm2 make psmisc python3 quota sed \
        uuid-dev uuid-runtime xfsprogs linux-headers-$(uname -r) sqlite3 make
$ sudo apt-get install f2fs-tools ocfs2-tools udftools xfsdump \
        xfslibs-dev
$ git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
$ cd xfstests-dev
$ make
$ sudo su
# mkdir /test
# mkdir /scratch
# mkfs.btrfs -f /dev/vdc
# cat << EOF >> ./local.config
export TEST_DEV=/dev/vdc
export TEST_DIR=/test
export SCRATCH_DEV=/dev/vdd
export SCRATCH_MNT=/scratch
EOF

# ./check btrfs/154

btrfs/154 _check_dmesg: something found in dmesg (see /home/ubuntu/xfstests-dev/results//btrfs/154.dmesg)
- output mismatch (see /home/ubuntu/xfstests-dev/results//btrfs/154.out.bad)
    --- tests/btrfs/154.out 2023-01-28 02:53:03.566450703 +0000
    +++ /home/ubuntu/xfstests-dev/results//btrfs/154.out.bad 2023-01-28 06:51:34.113121042 +0000
    @@ -1,2 +1,6 @@
     QA output created by 154
    +Traceback (most recent call last):
    + File "/home/ubuntu/xfstests-dev/src/btrfs_crc32c_forged_name.py", line 99, in <module>
    + os.rename(srcpath, dstpath)
    +OSError: [Errno 75] Value too large for defined data type: '/scratch/309' -> b'/scratch/fa5d\x90O\x97015d7a47c48fdeb99b857c17e8038da6382fcb05e3a6b367589a8f54a8c3c1327584dfa630b4bd8c5bbb37b4decc2b82fecb4c940e0bd0989166c44e6af2855e9e42a02a57cffa2fc5283525ac53b2b0d2baaf874ff50b'
Ran: btrfs/154
Failures: btrfs/154
Failed 1 of 1 tests

If you examine dmesg, you will see the oops from the impact section.

If you install the test kernel from the below ppa:

https://launchpad.net/~mruffell/+archive/ubuntu/sf349467-btrfs-154

The issue no longer occurs:

# ./check btrfs/154

Ran: btrfs/154
Passed all 1 tests

[Fix]

This was fixed in 5.11-rc3 by the below commit:

commit 9a664971569daf68254928149f580b4f5856d274
Author: ethanwu <email address hidden>
Date: Tue Dec 1 17:25:12 2020 +0800
Subject: btrfs: correctly calculate item size used when item key collision happens
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9a664971569daf68254928149f580b4f5856d274

This cherry-picks to Focal, and required a small backport to Bionic, removing the hunk that contained comments explaining the parameters to btrfs_search_slot().

[Where problems could occur]

Problems could occur when calculating the size required for btrfs_item and item data when hash collisions occur. Such collisions are rare in of itself, but possible if you have a large amount files or craft filenames to force collisions with the crc32 hash algorithm.

If a regression were to occur, it could cause more transactions to be aborted, and would likely result in the users volume being forced read only. They might not lose any existing data, but data being written might be lost.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-azure-4.15/4.15.0-1162.177 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'.

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!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux/5.4.0-145.162 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!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux/4.15.0-207.218 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'.

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!

[Matthew Ruffell (mruffell)]

Performing verification for Focal

I started a fresh VM with 5.4.0-144-generic from -updates. I attached 2x virtio
disks of 3gb each, for scratch disks.

I ran btrfs/154 with the following results:

# ./check btrfs/154
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 focal-xfs 5.4.0-144-generic #161-Ubuntu SMP Fri Feb 3 14:49:04 UTC 2023
MKFS_OPTIONS -- /dev/vdd
MOUNT_OPTIONS -- /dev/vdd /scratch

btrfs/154 4s ... _check_dmesg: something found in dmesg (see /home/ubuntu/xfstests-dev/results//btrfs/154.dmesg)
- output mismatch (see /home/ubuntu/xfstests-dev/results//btrfs/154.out.bad)
    --- tests/btrfs/154.out 2023-01-28 07:54:34.007433164 +0000
    +++ /home/ubuntu/xfstests-dev/results//btrfs/154.out.bad 2023-03-14 04:34:53.765899711 +0000
    @@ -1,2 +1,6 @@
     QA output created by 154
    +Traceback (most recent call last):
    + File "/home/ubuntu/xfstests-dev/src/btrfs_crc32c_forged_name.py", line 99, in <module>
    + os.rename(srcpath, dstpath)
    +OSError: [Errno 75] Value too large for defined data type: '/scratch/309' -> b'/scratch/69f3?u\x97\xf3c33c58c648a2a9686fad82dbf43d7bfb443de4698f629e5b2b95126d6382430b8f29e4f502ccf306254d24cfd3800cb04a305989253db49f699a83cc2bc5d86a4f9b235891c0f72ba344a34e41aa69f819f196f7dbf29'
     Silence is golden
    ...
    (Run 'diff -u /home/ubuntu/xfstests-dev/tests/btrfs/154.out /home/ubuntu/xfstests-dev/results//btrfs/154.out.bad' to see the entire diff)
Ran: btrfs/154
Failures: btrfs/154
Failed 1 of 1 tests

[ 49.889518] BTRFS info (device vdc): flagging fs with big metadata feature
[ 49.889520] BTRFS info (device vdc): disk space caching is enabled
[ 49.889521] BTRFS info (device vdc): has skinny extents
[ 49.891250] BTRFS info (device vdc): checking UUID tree
[ 50.007425] BTRFS: device fsid 382d436d-5f41-48a3-b96d-42c07ede9a03 devid 1 transid 5 /dev/vdd
[ 50.012807] BTRFS info (device vdd): flagging fs with big metadata feature
[ 50.012809] BTRFS info (device vdd): disk space caching is enabled
[ 50.012810] BTRFS info (device vdd): has skinny extents
[ 50.014307] BTRFS info (device vdd): checking UUID tree
[ 50.171099] BTRFS info (device vdc): flagging fs with big metadata feature
[ 50.171102] BTRFS info (device vdc): disk space caching is enabled
[ 50.171103] BTRFS info (device vdc): has skinny extents
[ 50.204928] run fstests btrfs/154 at 2023-03-14 04:34:47
[ 50.378091] BTRFS: device fsid 68eee97a-92e0-47da-9d5e-c6c8312ee358 devid 1 transid 5 /dev/vdd
[ 50.393188] BTRFS info (device vdd): flagging fs with big metadata feature
[ 50.393191] BTRFS info (device vdd): disk space caching is enabled
[ 50.393193] BTRFS info (device vdd): has skinny extents
[ 50.401657] BTRFS info (device vdd): checking UUID tree
[ 56.084117] ------------[ cut here ]------------
[ 56.084121] BTRFS: Transaction aborted (error -75)
[ 56.084229] WARNING: CPU: 2 PID: 1741 at fs/btrfs/inode.c:10148 btrfs_rename+0x9c6/0xa40 [btrfs]
[ 56.084265] CPU: 2 PID: 1741 Comm: python3 Not tainted 5.4.0-144-generic #161-Ubuntu
[ 56.084267] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-debian-1.16.0-4 04/01/2014
[ 56.084302] RIP: 0010:btrfs_rename+0x9c6/0xa40...

[Matthew Ruffell (mruffell)]

Performing verification for Bionic

I started a fresh VM with 4.15.0-206-generic from -updates. I attached 2x virtio
disks of 3gb each, for scratch disks.

I ran btrfs/154 with the following results:

# ./check btrfs/154
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 bionic-xfs 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023
MKFS_OPTIONS -- /dev/vdd
MOUNT_OPTIONS -- /dev/vdd /scratch

btrfs/154 4s ... _check_dmesg: something found in dmesg (see /home/ubuntu/xfstests-dev/results//btrfs/154.dmesg)
- output mismatch (see /home/ubuntu/xfstests-dev/results//btrfs/154.out.bad)
    --- tests/btrfs/154.out 2023-01-28 02:53:03.566450703 +0000
    +++ /home/ubuntu/xfstests-dev/results//btrfs/154.out.bad 2023-03-14 04:46:12.824848412 +0000
    @@ -1,2 +1,6 @@
     QA output created by 154
    +Traceback (most recent call last):
    + File "/home/ubuntu/xfstests-dev/src/btrfs_crc32c_forged_name.py", line 99, in <module>
    + os.rename(srcpath, dstpath)
    +OSError: [Errno 75] Value too large for defined data type: '/scratch/309' -> b'/scratch/ec73\xb4\xd3?\xc4249e4acad9bcfc483738ce72c1da9a5e0dcc098e3103a2e00d8e05fe6a463df2c472d5df948dc08e6aaf48cdff3c41de690ce50cd88be6cdea40e616db44152df10f8dfe36a5de62550b277db85c01455dde98b189b68'
     Silence is golden
    ...
    (Run 'diff -u /home/ubuntu/xfstests-dev/tests/btrfs/154.out /home/ubuntu/xfstests-dev/results//btrfs/154.out.bad' to see the entire diff)
Ran: btrfs/154
Failures: btrfs/154
Failed 1 of 1 tests

[ 69.108117] BTRFS: device fsid 032cd7d2-e729-4a6a-aa6d-95141191525a devid 1 transid 5 /dev/vdc
[ 78.693183] BTRFS info (device vdc): disk space caching is enabled
[ 78.693184] BTRFS info (device vdc): has skinny extents
[ 78.693185] BTRFS info (device vdc): flagging fs with big metadata feature
[ 78.695928] BTRFS info (device vdc): creating UUID tree
[ 78.828837] BTRFS: device fsid 053e2dfb-59fb-45ab-8a69-08262d44d669 devid 1 transid 5 /dev/vdd
[ 78.840701] BTRFS info (device vdd): disk space caching is enabled
[ 78.840703] BTRFS info (device vdd): has skinny extents
[ 78.840704] BTRFS info (device vdd): flagging fs with big metadata feature
[ 78.843953] BTRFS info (device vdd): creating UUID tree
[ 79.053524] BTRFS info (device vdc): disk space caching is enabled
[ 79.053526] BTRFS info (device vdc): has skinny extents
[ 79.104532] run fstests btrfs/154 at 2023-03-14 04:46:08
[ 79.230124] BTRFS: device fsid af57acbb-7a45-46e8-969f-4cb3ce52e29e devid 1 transid 5 /dev/vdd
[ 79.235760] BTRFS info (device vdd): disk space caching is enabled
[ 79.235761] BTRFS info (device vdd): has skinny extents
[ 79.235761] BTRFS info (device vdd): flagging fs with big metadata feature
[ 79.239893] BTRFS info (device vdd): creating UUID tree
[ 82.714095] ------------[ cut here ]------------
[ 82.714098] BTRFS: Transaction aborted (error -75)
[ 82.714180] WARNING: CPU: 2 PID: 1883 at /build/linux-sIqTXt/linux-4.15.0/fs/btrfs/inode.c:10217 btrfs_rename+0xcf1/0xdf0 [btrfs]
[ 82.714210] CPU: 2 PID: 1883 Comm: python3 Not tainted 4.15.0-206-generic #217-Ubuntu
[ 82.714212] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-debian-1.16.0-4...

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 5.4.0-146.163

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

  * focal/linux: 5.4.0-146.163 -proposed tracker (LP: #2012094)

  * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
    - NFS: Correct timing for assigning access cache timestamp

linux (5.4.0-145.162) focal; urgency=medium

  * focal/linux: 5.4.0-145.162 -proposed tracker (LP: #2008389)

  * [SRU]Update ice driver to support E823 devices (LP: #1986717)
    - ice: Add device ids for E822 devices
    - ice: add support for E823 devices

  * btrfs/154: rename fails with EOVERFLOW when calculating item size during
    item key collision (LP: #2004132)
    - btrfs: correctly calculate item size used when item key collision happens

  * rtcpie in timers from ubuntu_kernel_selftests randomly failing
    (LP: #1814234)
    - SAUCE: selftest: rtcpie: Force passing unreliable subtest

  * [UBUNTU 20.04] KVM: s390: pv: don't allow userspace to set the clock under
    PV - kernel part (LP: #1999882)
    - KVM: s390x: fix SCK locking
    - KVM: s390: pv: don't allow userspace to set the clock under PV

  * CVE-2021-3669
    - ipc: replace costly bailout check in sysvipc_find_ipc()

  * net:fcnal-test.sh 'nettest' command not found on F/K (LP: #2006391)
    - selftests/net: Find nettest in current directory

  * xfs: Preallocated ioend transactions cause deadlock due to log buffer
    exhaustion (LP: #2007219)
    - xfs: drop submit side trans alloc for append ioends

  * CVE-2022-4382
    - USB: gadgetfs: Fix race between mounting and unmounting

  * CVE-2022-2196
    - KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS

  * ubuntu_kernel_selftests: net:udpgso_bench.sh failed (LP: #1951447)
    - selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs

  * net:fcnal-test.sh didn't return a non-zero value even with some sub-tests
    failed (LP: #2006692)
    - selftests: net/fcnal-test.sh: add exit code

  * Fix selftests/ftracetests/Meta-selftests in Focal (LP: #2006453)
    - SAUCE: Fix ftrace/Meta-selftests bashism check

  * CVE-2023-23559
    - wifi: rndis_wlan: Prevent buffer overflow in rndis_query_oid

 -- Luke Nowakowski-Krijger <email address hidden> Fri, 17 Mar 2023 11:08:20 -0700

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 4.15.0-208.220

---------------
linux (4.15.0-208.220) bionic; urgency=medium

  * bionic/linux: 4.15.0-208.220 -proposed tracker (LP: #2012097)

  * NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
    - NFS: Correct timing for assigning access cache timestamp

linux (4.15.0-207.218) bionic; urgency=medium

  * bionic/linux: 4.15.0-207.218 -proposed tracker (LP: #2008419)

  * rtcpie in timers from ubuntu_kernel_selftests randomly failing
    (LP: #1814234)
    - SAUCE: selftest: rtctest: Force passing unreliable subtest

  * btrfs/154: rename fails with EOVERFLOW when calculating item size during
    item key collision (LP: #2004132)
    - btrfs: correctly calculate item size used when item key collision happens

  * CVE-2021-3669
    - ipc: replace costly bailout check in sysvipc_find_ipc()

  * Bionic update: upstream stable patchset 2023-02-06 (LP: #2006403)
    - libtraceevent: Fix build with binutils 2.35
    - once: Fix panic when module unload
    - once: add DO_ONCE_SLOW() for sleepable contexts
    - mm/khugepaged: fix GUP-fast interaction by sending IPI
    - mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths
    - block: unhash blkdev part inode when the part is deleted
    - ASoC: ops: Check bounds for second channel in snd_soc_put_volsw_sx()
    - can: sja1000: fix size of OCR_MODE_MASK define
    - can: mcba_usb: Fix termination command argument
    - ASoC: ops: Correct bounds check for second channel on SX controls
    - perf script python: Remove explicit shebang from tests/attr.c
    - udf: Discard preallocation before extending file with a hole
    - udf: Drop unused arguments of udf_delete_aext()
    - udf: Fix preallocation discarding at indirect extent boundary
    - udf: Do not bother looking for prealloc extents if i_lenExtents matches
      i_size
    - udf: Fix extending file within last block
    - usb: gadget: uvc: Prevent buffer overflow in setup handler
    - USB: serial: option: add Quectel EM05-G modem
    - USB: serial: cp210x: add Kamstrup RF sniffer PIDs
    - igb: Initialize mailbox message for VF reset
    - net: loopback: use NET_NAME_PREDICTABLE for name_assign_type
    - usb: musb: remove extra check in musb_gadget_vbus_draw
    - ARM: dts: qcom: apq8064: fix coresight compatible
    - drivers: soc: ti: knav_qmss_queue: Mark knav_acc_firmwares as static
    - arm: dts: spear600: Fix clcd interrupt
    - soc: ti: smartreflex: Fix PM disable depth imbalance in omap_sr_probe
    - arm64: dts: mediatek: mt6797: Fix 26M oscillator unit name
    - ARM: dts: dove: Fix assigned-addresses for every PCIe Root Port
    - ARM: dts: armada-370: Fix assigned-addresses for every PCIe Root Port
    - ARM: dts: armada-xp: Fix assigned-addresses for every PCIe Root Port
    - ARM: dts: armada-375: Fix assigned-addresses for every PCIe Root Port
    - ARM: dts: armada-38x: Fix assigned-addresses for every PCIe Root Port
    - ARM: dts: armada-39x: Fix assigned-addresses for every PCIe Root Port
    - ARM: dts: turris-omnia: Add ethernet aliases
    - ARM: dts: turris-omnia: Add switch port 6 node
    - pstore/ram: Fix error return code in...

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-aws/5.4.0-1100.108 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!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-azure/5.4.0-1106.112 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!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66 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!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-snapdragon/4.15.0-1148.158 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'.

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!

[Roxana Nicolescu (roxanan)]

bionic:linux-snapdragon was not released last cycle, hence it asks for verification again.
Given that the main kernel was verified, I will mark this as verified as well.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-xilinx-zynqmp/5.4.0-1023.27 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!