ubuntu-kernel-tests

memfd from ubuntu_kernel_selftests failed to build on B-5.4 (unknown type name ‘__u64’)

Bug #1944613 reported by Luke Nowakowski-Krijger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
New
Undecided
Luke Nowakowski-Krijger
linux (Ubuntu)
Fix Released
Undecided
Unassigned
Bionic
Invalid
Undecided
Unassigned
Focal
Fix Released
Undecided
Unassigned
linux-hwe-5.4 (Ubuntu)
Invalid
Undecided
Unassigned
Bionic
Fix Released
Undecided
Unassigned
Focal
Invalid
Undecided
Unassigned

Bug Description

[Impact]
BugLink: https://bugs.launchpad.net/bugs/1944613

There are build issues in selftests/memfd/fuse_test.c where __u64 is not
defined. This is issue is probably due to the fact that in 5.4 there is
a type include in one of the includes in the file, however this include
probably was not there for 4.15. Regardless we fix this by including the
type file directly.

[Fix]
* selftests/memfd: fix __u64 not defined build issue
Add #include <asm/types.h> to define the type

[Test Plan]
Recompile tests to make sure they build and tests pass.

[Where problems could occur]
Should be no problems since we are adding an include file that userspace
files always have access to.

--------------------------------------------------------------------------

Failed to build on B/linux-hwe-5.4 5.4.0-85.95~18.04.1. This was observed in previous cycles.
I am working on a fix for it right now.

  13203 fuse_test.c:63:8: error: unknown type name ‘__u64’
      13204 static __u64 mfd_assert_get_seals(int fd)
      13205 ^~~~~
      13206 fuse_test.c:76:42: error: unknown type name ‘__u64’; did you mean ‘__f64’?
      13207 static void mfd_assert_has_seals(int fd, __u64 seals)
      13208 ^~~~~
      13209 __f64
      13210 fuse_test.c:88:42: error: unknown type name ‘__u64’; did you mean ‘__f64’?
      13211 static void mfd_assert_add_seals(int fd, __u64 seals)
      13212 ^~~~~
      13213 __f64
      13214 fuse_test.c:102:39: error: unknown type name ‘__u64’; did you mean ‘__f64’?
      13215 static int mfd_busy_add_seals(int fd, __u64 seals)
      13216 ^~~~~
      13217 __f64
      13218 fuse_test.c: In function ‘sealing_thread_fn’:
      13219 fuse_test.c:185:6: warning: implicit declaration of function ‘mfd_busy_add_seals’; did you mean ‘mfd_assert_get_seals’? [-Wimplicit-function-declaration]
      13220 r = mfd_busy_add_seals(global_mfd, F_SEAL_WRITE);
      13221 ^~~~~~~~~~~~~~~~~~
      13222 mfd_assert_get_seals
      13223 fuse_test.c:193:3: warning: implicit declaration of function ‘mfd_assert_add_seals’; did you mean ‘mfd_assert_get_seals’? [-Wimplicit-function-declaration]
      13224 mfd_assert_add_seals(global_mfd, F_SEAL_WRITE);
      13225 ^~~~~~~~~~~~~~~~~~~~
      13226 mfd_assert_get_seals
      13227 fuse_test.c: In function ‘main’:
      13228 fuse_test.c:302:2: warning: implicit declaration of function ‘mfd_assert_has_seals’; did you mean ‘mfd_assert_get_seals’? [-Wimplicit-function-declaration]
      13229 mfd_assert_has_seals(mfd, F_SEAL_WRITE);
      13230 ^~~~~~~~~~~~~~~~~~~~
      13231 mfd_assert_get_seals
      13232 make[1]: *** [/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/fuse_test] Error 1
      13233 make: *** [all] Error 2

See original description
Luke Nowakowski-Krijger (lukenow)
Changed in ubuntu-kernel-tests:
assignee: nobody → Luke Nowakowski-Krijger (lukenow)
Luke Nowakowski-Krijger (lukenow)
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1944613

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Kleber Sacilotto de Souza (kleber-souza)
Changed in linux (Ubuntu Focal):
status: New → In Progress
Changed in linux (Ubuntu):
status: Incomplete → Fix Released
Changed in linux-hwe-5.4 (Ubuntu Focal):
status: New → Invalid
Changed in linux-hwe-5.4 (Ubuntu Bionic):
status: New → In Progress
Changed in linux (Ubuntu Bionic):
status: New → Invalid
Changed in linux-hwe-5.4 (Ubuntu):
status: New → Invalid
Kelsey Steele (kelsey-steele)
Changed in linux (Ubuntu Focal):
status: In Progress → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/5.4.0-90.101 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
Luke Nowakowski-Krijger (lukenow)
tags: added: verification-done-focal
removed: verification-needed-focal
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (32.8 KiB)

This bug was fixed in the package linux-hwe-5.4 - 5.4.0-90.101~18.04.1

---------------
linux-hwe-5.4 (5.4.0-90.101~18.04.1) bionic; urgency=medium

  * bionic/linux-hwe-5.4: 5.4.0-90.101~18.04.1 -proposed tracker (LP: #1947259)

  * Packaging resync (LP: #1786013)
    - [Packaging] update Ubuntu.md

  [ Ubuntu: 5.4.0-90.101 ]

  * focal/linux: 5.4.0-90.101 -proposed tracker (LP: #1947260)
  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2021.10.18)
  * Add final-checks to check certificates (LP: #1947174)
    - [Packaging] Add system trusted and revocation keys final check
  * No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s
    Gen2 (LP: #1939052)
    - ALSA: hda/realtek: Quirks to enable speaker output for Lenovo Legion 7i
      15IMHG05, Yoga 7i 14ITL5/15ITL5, and 13s Gen2 laptops.
    - ALSA: hda/realtek: Fix for quirk to enable speaker output on the Lenovo 13s
      Gen2
  * CVE-2020-36385
    - RDMA/cma: Add missing locking to rdma_accept()
    - RDMA/ucma: Fix the locking of ctx->file
    - RDMA/ucma: Rework ucma_migrate_id() to avoid races with destroy
  * Focal update: v5.4.148 upstream stable release (LP: #1946802)
    - rtc: tps65910: Correct driver module alias
    - btrfs: wake up async_delalloc_pages waiters after submit
    - btrfs: reset replace target device to allocation state on close
    - blk-zoned: allow zone management send operations without CAP_SYS_ADMIN
    - blk-zoned: allow BLKREPORTZONE without CAP_SYS_ADMIN
    - PCI/MSI: Skip masking MSI-X on Xen PV
    - powerpc/perf/hv-gpci: Fix counter value parsing
    - xen: fix setting of max_pfn in shared_info
    - include/linux/list.h: add a macro to test if entry is pointing to the head
    - 9p/xen: Fix end of loop tests for list_for_each_entry
    - tools/thermal/tmon: Add cross compiling support
    - pinctrl: stmfx: Fix hazardous u8[] to unsigned long cast
    - pinctrl: ingenic: Fix incorrect pull up/down info
    - soc: qcom: aoss: Fix the out of bound usage of cooling_devs
    - soc: aspeed: lpc-ctrl: Fix boundary check for mmap
    - soc: aspeed: p2a-ctrl: Fix boundary check for mmap
    - arm64: head: avoid over-mapping in map_memory
    - crypto: public_key: fix overflow during implicit conversion
    - block: bfq: fix bfq_set_next_ioprio_data()
    - power: supply: max17042: handle fails of reading status register
    - dm crypt: Avoid percpu_counter spinlock contention in crypt_page_alloc()
    - VMCI: fix NULL pointer dereference when unmapping queue pair
    - media: uvc: don't do DMA on stack
    - media: rc-loopback: return number of emitters rather than error
    - Revert "dmaengine: imx-sdma: refine to load context only once"
    - dmaengine: imx-sdma: remove duplicated sdma_load_context
    - libata: add ATA_HORKAGE_NO_NCQ_TRIM for Samsung 860 and 870 SSDs
    - ARM: 9105/1: atags_to_fdt: don't warn about stack size
    - PCI/portdrv: Enable Bandwidth Notification only if port supports it
    - PCI: Restrict ASMedia ASM1062 SATA Max Payload Size Supported
    - PCI: Return ~0 data on pciconfig_read() CAP_SYS_ADMIN failure
    - PCI: xilinx-nwl: Enable the clock through CCF
  ...

Changed in linux-hwe-5.4 (Ubuntu Bionic):
status: In Progress → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (32.6 KiB)

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

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

  * focal/linux: 5.4.0-90.101 -proposed tracker (LP: #1947260)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2021.10.18)

  * Add final-checks to check certificates (LP: #1947174)
    - [Packaging] Add system trusted and revocation keys final check

  * No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s
    Gen2 (LP: #1939052)
    - ALSA: hda/realtek: Quirks to enable speaker output for Lenovo Legion 7i
      15IMHG05, Yoga 7i 14ITL5/15ITL5, and 13s Gen2 laptops.
    - ALSA: hda/realtek: Fix for quirk to enable speaker output on the Lenovo 13s
      Gen2

  * CVE-2020-36385
    - RDMA/cma: Add missing locking to rdma_accept()
    - RDMA/ucma: Fix the locking of ctx->file
    - RDMA/ucma: Rework ucma_migrate_id() to avoid races with destroy

  * Focal update: v5.4.148 upstream stable release (LP: #1946802)
    - rtc: tps65910: Correct driver module alias
    - btrfs: wake up async_delalloc_pages waiters after submit
    - btrfs: reset replace target device to allocation state on close
    - blk-zoned: allow zone management send operations without CAP_SYS_ADMIN
    - blk-zoned: allow BLKREPORTZONE without CAP_SYS_ADMIN
    - PCI/MSI: Skip masking MSI-X on Xen PV
    - powerpc/perf/hv-gpci: Fix counter value parsing
    - xen: fix setting of max_pfn in shared_info
    - include/linux/list.h: add a macro to test if entry is pointing to the head
    - 9p/xen: Fix end of loop tests for list_for_each_entry
    - tools/thermal/tmon: Add cross compiling support
    - pinctrl: stmfx: Fix hazardous u8[] to unsigned long cast
    - pinctrl: ingenic: Fix incorrect pull up/down info
    - soc: qcom: aoss: Fix the out of bound usage of cooling_devs
    - soc: aspeed: lpc-ctrl: Fix boundary check for mmap
    - soc: aspeed: p2a-ctrl: Fix boundary check for mmap
    - arm64: head: avoid over-mapping in map_memory
    - crypto: public_key: fix overflow during implicit conversion
    - block: bfq: fix bfq_set_next_ioprio_data()
    - power: supply: max17042: handle fails of reading status register
    - dm crypt: Avoid percpu_counter spinlock contention in crypt_page_alloc()
    - VMCI: fix NULL pointer dereference when unmapping queue pair
    - media: uvc: don't do DMA on stack
    - media: rc-loopback: return number of emitters rather than error
    - Revert "dmaengine: imx-sdma: refine to load context only once"
    - dmaengine: imx-sdma: remove duplicated sdma_load_context
    - libata: add ATA_HORKAGE_NO_NCQ_TRIM for Samsung 860 and 870 SSDs
    - ARM: 9105/1: atags_to_fdt: don't warn about stack size
    - PCI/portdrv: Enable Bandwidth Notification only if port supports it
    - PCI: Restrict ASMedia ASM1062 SATA Max Payload Size Supported
    - PCI: Return ~0 data on pciconfig_read() CAP_SYS_ADMIN failure
    - PCI: xilinx-nwl: Enable the clock through CCF
    - PCI: aardvark: Fix checking for PIO status
    - PCI: aardvark: Increase polling delay to 1.5s while waiting for PIO response
    - PCI: aardvark: Fix masking and unmasking legacy INTx interrupts
    - HID...

Changed in linux (Ubuntu Focal):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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