ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-kvm / L-kvm

Bug #1977827 reported by Po-Hsu Lin
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Fix Committed
Undecided
Unassigned
linux (Ubuntu)
Invalid
Medium
Unassigned
Jammy
Fix Released
Medium
Unassigned
Kinetic
Fix Committed
Medium
Unassigned
Lunar
Fix Released
Medium
Unassigned

Bug Description

(Thibf got this issue fixed for KVM kernels, for PPC please refer to bug 2026592)

Issue found on Jammy 5.15.0-36.37 with Power9 node baltar

Test failed with:
# [15] Generic dynamic event - check if duplicate events are caught [FAIL]

Test Log:
 make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
 TAP version 13
 1..1
 # selftests: ftrace: ftracetest
 # === Ftrace unit tests ===
 # [1] Basic trace file check [PASS]
 # [2] Basic test for tracers [PASS]
 # [3] Basic trace clock test [PASS]
 # [4] Basic event tracing check [PASS]
 # [5] Change the ringbuffer size [PASS]
 # [6] Snapshot and tracing setting [PASS]
 # [7] trace_pipe and trace_marker [PASS]
 # [8] Test ftrace direct functions against tracers [UNRESOLVED]
 # [9] Test ftrace direct functions against kprobes [UNRESOLVED]
 # [10] Generic dynamic event - add/remove eprobe events [PASS]
 # [11] Generic dynamic event - add/remove kprobe events [PASS]
 # [12] Generic dynamic event - add/remove synthetic events [PASS]
 # [13] Generic dynamic event - selective clear (compatibility) [PASS]
 # [14] Generic dynamic event - generic clear event [PASS]
 # [15] Generic dynamic event - check if duplicate events are caught [FAIL]
 # [16] event tracing - enable/disable with event level files [PASS]
 # [17] event tracing - restricts events based on pid notrace filtering [PASS]
 # [18] event tracing - restricts events based on pid [PASS]
 # [19] event tracing - enable/disable with subsystem level files [PASS]
 # [20] event tracing - enable/disable with top level files [PASS]
 # [21] Test trace_printk from module [PASS]
 # [22] ftrace - function graph filters with stack tracer [PASS]
 # [23] ftrace - function graph filters [PASS]
 # [24] ftrace - function pid notrace filters [PASS]
 # [25] ftrace - function pid filters [PASS]
 # [26] ftrace - stacktrace filter command [PASS]
 # [27] ftrace - function trace with cpumask [PASS]
 # [28] ftrace - test for function event triggers [PASS]
 # [29] ftrace - function trace on module [PASS]
 # [30] ftrace - function profiling [PASS]
 # [31] ftrace - function profiler with function tracing [PASS]
 # [32] ftrace - test reading of set_ftrace_filter [PASS]
 # [33] ftrace - test for function traceon/off triggers [PASS]
 # [34] ftrace - test tracing error log support [PASS]
 # [35] Test creation and deletion of trace instances while setting an event [PASS]
 # [36] Test creation and deletion of trace instances [PASS]
 # [37] Kprobe dynamic event - adding and removing [PASS]
 # [38] Kprobe dynamic event - busy event check [PASS]
 # [39] Kprobe dynamic event with arguments [PASS]
 # [40] Kprobe event with comm arguments [PASS]
 # [41] Kprobe event string type argument [PASS]
 # [42] Kprobe event symbol argument [PASS]
 # [43] Kprobe event argument syntax [PASS]
 # [44] Kprobes event arguments with types [PASS]
 # [45] Kprobe event user-memory access [UNSUPPORTED]
 # [46] Kprobe event auto/manual naming [PASS]
 # [47] Kprobe dynamic event with function tracer [PASS]
 # [48] Create/delete multiprobe on kprobe event [PASS]
 # [49] Kprobe event parser error log check [PASS]
 # [50] Kretprobe dynamic event with arguments [PASS]
 # [51] Kretprobe dynamic event with maxactive [PASS]
 # [52] Kretprobe %return suffix test [PASS]
 # [53] Register/unregister many kprobe events [PASS]
 # [54] Kprobe profile [PASS]
 # [55] Uprobe event parser error log check [PASS]
 # [56] test for the preemptirqsoff tracer [UNSUPPORTED]
 # [57] Meta-selftest: Checkbashisms [PASS]
 # [58] Test wakeup tracer [PASS]
 # [59] Test wakeup RT tracer [PASS]
 # [60] event trigger - test inter-event histogram trigger expected fail actions [XFAIL]
 # [61] event trigger - test field variable support [PASS]
 # [62] event trigger - test multiple actions on hist trigger [PASS]
 # [63] event trigger - test inter-event histogram trigger onchange action [PASS]
 # [64] event trigger - test inter-event histogram trigger onmatch action [PASS]
 # [65] event trigger - test inter-event histogram trigger onmatch-onmax action [PASS]
 # [66] event trigger - test inter-event histogram trigger onmax action [PASS]
 # [67] event trigger - test inter-event histogram trigger snapshot action [PASS]
 # [68] event trigger - test inter-event histogram trigger eprobe on synthetic event [PASS]
 # [69] event trigger - test inter-event histogram trigger trace action with dynamic string param [PASS]
 # [70] event trigger - test synthetic_events syntax parser [PASS]
 # [71] event trigger - test synthetic_events syntax parser errors [PASS]
 # [72] event trigger - test inter-event histogram trigger trace action [PASS]
 # [73] event trigger - test event enable/disable trigger [PASS]
 # [74] event trigger - test trigger filter [PASS]
 # [75] event trigger - test histogram modifiers [PASS]
 # [76] event trigger - test histogram parser errors [PASS]
 # [77] event trigger - test multiple histogram triggers [PASS]
 # [78] event trigger - test snapshot-trigger [PASS]
 # [79] event trigger - test stacktrace-trigger [PASS]
 # [80] trace_marker trigger - test snapshot trigger [PASS]
 # [81] trace_marker trigger - test histogram with synthetic event against kernel event [PASS]
 # [82] trace_marker trigger - test histogram with synthetic event [PASS]
 # [83] event trigger - test traceon/off trigger [PASS]
 # [84] (instance) Basic test for tracers [PASS]
 # [85] (instance) Basic trace clock test [PASS]
 # [86] (instance) Change the ringbuffer size [PASS]
 # [87] (instance) Snapshot and tracing setting [PASS]
 # [88] (instance) trace_pipe and trace_marker [PASS]
 # [89] (instance) event tracing - enable/disable with event level files [PASS]
 # [90] (instance) event tracing - restricts events based on pid notrace filtering [PASS]
 # [91] (instance) event tracing - restricts events based on pid [PASS]
 # [92] (instance) event tracing - enable/disable with subsystem level files [PASS]
 # [93] (instance) ftrace - function pid notrace filters [PASS]
 # [94] (instance) ftrace - function pid filters [PASS]
 # [95] (instance) ftrace - stacktrace filter command [PASS]
 # [96] (instance) ftrace - test for function event triggers [PASS]
 # [97] (instance) ftrace - test for function traceon/off triggers [PASS]
 # [98] (instance) event trigger - test event enable/disable trigger [PASS]
 # [99] (instance) event trigger - test trigger filter [PASS]
 # [100] (instance) event trigger - test histogram modifiers [PASS]
 # [101] (instance) event trigger - test multiple histogram triggers [PASS]
 # [102] (instance) trace_marker trigger - test snapshot trigger [PASS]
 #
 #
 # # of passed: 96
 # # of failed: 1
 # # of unresolved: 2
 # # of untested: 0
 # # of unsupported: 2
 # # of xfailed: 1
 # # of undefined(test bug): 0
 not ok 1 selftests: ftrace: ftracetest # exit=1

This is not a regression, I can see this issue with 5.15.0-30.31 as well.
We just don't have a bug report for this.

Po-Hsu Lin (cypressyew)
tags: added: sru-20220509 sru-20220530 ubuntu-kernel-selftests
tags: added: 5.15 jammy ppc64el
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 1977827

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
Changed in linux (Ubuntu Jammy):
status: New → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote : Re: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9

This is also affecting J-kvm

tags: added: sru-20230320
summary: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events
- are caught" on J-5.15 P9
+ are caught" on J-5.15 P9 / J-kvm
Revision history for this message
Thibf (thibf) wrote : Re: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm

kprobe_events are not available (seems related to CONFIG_KALLSYMS disabled) and this test `tools/testing/selftests/ftrace/test.d/dynevent/test_duplicates.tc` doesn't seems to works well in this case as it fails quickly:
```
+ echo e:egroup/eevent syscalls/sys_enter_openat file=+0($filename):ustring
./ftracetest: 18: echo: echo: I/O error
```

summary: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events
- are caught" on J-5.15 P9 / J-kvm
+ are caught" on J-5.15 P9 / J-kvm / L-kvm
Stefan Bader (smb)
Changed in linux (Ubuntu Jammy):
importance: Undecided → Medium
status: Incomplete → Fix Committed
Changed in linux (Ubuntu Lunar):
importance: Undecided → Medium
status: New → Fix Committed
Changed in linux (Ubuntu):
status: Incomplete → In Progress
importance: Undecided → Medium
Changed in linux (Ubuntu Kinetic):
importance: Undecided → Medium
status: New → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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: kernel-spammed-jammy-linux verification-needed-jammy
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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: kernel-spammed-lunar-linux verification-needed-lunar
Thibf (thibf)
tags: added: verification-done-jammy verification-done-lunar
removed: verification-needed-jammy verification-needed-lunar
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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: kernel-spammed-kinetic-linux verification-needed-kinetic
Thibf (thibf)
Changed in ubuntu-kernel-tests:
status: New → Fix Committed
Thibf (thibf)
tags: added: verification-done-kinetic
removed: verification-needed-kinetic
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (10.4 KiB)

This bug was fixed in the package linux - 6.2.0-25.25

---------------
linux (6.2.0-25.25) lunar; urgency=medium

  * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167)

  * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
    caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827)
    - SAUCE: selftests/ftrace: Add test dependency

  * Add microphone support of the front headphone port on P3 Tower
    (LP: #2023650)
    - ALSA: hda/realtek: Add Lenovo P3 Tower platform

  * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539)
    - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6

  * Fix Disable thunderbolt clx make edp-monitor garbage while moving the
    touchpad (LP: #2023004)
    - drm/i915: Use 18 fast wake AUX sync len

  * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C
    dongle (LP: #2021949)
    - thunderbolt: Increase timeout of DP OUT adapter handshake
    - thunderbolt: Do not touch CL state configuration during discovery
    - thunderbolt: Increase DisplayPort Connection Manager handshake timeout

  * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591)
    - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs

  * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433)
    - r8169: use spinlock to protect mac ocp register access
    - r8169: use spinlock to protect access to registers Config2 and Config5
    - r8169: enable cfg9346 config register access in atomic context
    - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context
    - r8169: disable ASPM during NAPI poll
    - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll

  * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package
    (LP: #2021605)
    - [Packaging] introduce do_lib_rust and enable it only on generic amd64

  * System either hang with black screen or rebooted on entering suspend on AMD
    Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685)
    - drm/amdgpu: refine get gpu clock counter method
    - drm/amdgpu/gfx11: update gpu_clock_counter logic

  * generate linux-lib-rust only on amd64 (LP: #2020356)
    - [Packaging] generate linux-lib-rust only on amd64

  * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062)
    - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table

  * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
    (LP: #1988806)
    - SAUCE: Add mdev_set_iommu_device() kABI.

  * Enable audio LEDs on HP laptops (LP: #2019915)
    - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop
    - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop

  * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root
    images (LP: #2019040)
    - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y

  * Lunar update: v6.2.13 upstream stable release (LP: #2023929)
    - ARM: dts: rockchip: fix a typo error for rk3288 spdif node
    - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz
    - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node
    - arm64: dts: qcom: ipq8074-hk10: ...

Changed in linux (Ubuntu Lunar):
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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: kernel-spammed-lunar-linux-riscv verification-needed-lunar
removed: verification-done-lunar
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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: kernel-spammed-lunar-linux-azure
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-hwe-6.2/6.2.0-26.26~22.04.1 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

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: kernel-spammed-jammy-linux-hwe-6.2 verification-needed-jammy
removed: verification-done-jammy
Revision history for this message
Po-Hsu Lin (cypressyew) wrote (last edit ):

Test is good on L-azure and j-hwe-6.2 6.2.0-26.26~22.04.1

tags: added: verification-done-jammy verification-done-lunar
removed: verification-needed-jammy verification-needed-lunar
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-tegra-igx/5.15.0-1002.2 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

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: kernel-spammed-jammy-linux-nvidia-tegra-igx verification-needed-jammy
removed: verification-done-jammy
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-tegra-5.15/5.15.0-1016.16~20.04.1 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: kernel-spammed-focal-linux-nvidia-tegra-5.15 verification-needed-focal
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-tegra/5.15.0-1016.16 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

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: kernel-spammed-jammy-linux-nvidia-tegra
Po-Hsu Lin (cypressyew)
tags: added: verification-done-focal
removed: verification-needed-focal
tags: added: verification-done-jammy
removed: verification-needed-jammy
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (83.7 KiB)

This bug was fixed in the package linux - 5.15.0-79.86

---------------
linux (5.15.0-79.86) jammy; urgency=medium

  * jammy/linux: 5.15.0-79.86 -proposed tracker (LP: #2026531)

  * Jammy update: v5.15.111 upstream stable release (LP: #2025095)
    - ASOC: Intel: sof_sdw: add quirk for Intel 'Rooks County' NUC M15
    - ASoC: soc-pcm: fix hw->formats cleared by soc_pcm_hw_init() for dpcm
    - x86/hyperv: Block root partition functionality in a Confidential VM
    - iio: adc: palmas_gpadc: fix NULL dereference on rmmod
    - ASoC: Intel: bytcr_rt5640: Add quirk for the Acer Iconia One 7 B1-750
    - selftests mount: Fix mount_setattr_test builds failed
    - asm-generic/io.h: suppress endianness warnings for readq() and writeq()
    - x86/cpu: Add model number for Intel Arrow Lake processor
    - wireguard: timers: cast enum limits members to int in prints
    - wifi: mt76: mt7921e: Set memory space enable in PCI_COMMAND if unset
    - arm64: Always load shadow stack pointer directly from the task struct
    - arm64: Stash shadow stack pointer in the task struct on interrupt
    - PCI: pciehp: Fix AB-BA deadlock between reset_lock and device_lock
    - PCI: qcom: Fix the incorrect register usage in v2.7.0 config
    - IMA: allow/fix UML builds
    - USB: dwc3: fix runtime pm imbalance on probe errors
    - USB: dwc3: fix runtime pm imbalance on unbind
    - hwmon: (k10temp) Check range scale when CUR_TEMP register is read-write
    - hwmon: (adt7475) Use device_property APIs when configuring polarity
    - posix-cpu-timers: Implement the missing timer_wait_running callback
    - blk-mq: release crypto keyslot before reporting I/O complete
    - blk-crypto: make blk_crypto_evict_key() return void
    - blk-crypto: make blk_crypto_evict_key() more robust
    - ext4: use ext4_journal_start/stop for fast commit transactions
    - staging: iio: resolver: ads1210: fix config mode
    - tty: Prevent writing chars during tcsetattr TCSADRAIN/FLUSH
    - xhci: fix debugfs register accesses while suspended
    - tick/nohz: Fix cpu_is_hotpluggable() by checking with nohz subsystem
    - MIPS: fw: Allow firmware to pass a empty env
    - ipmi:ssif: Add send_retries increment
    - ipmi: fix SSIF not responding under certain cond.
    - kheaders: Use array declaration instead of char
    - wifi: mt76: add missing locking to protect against concurrent rx/status
      calls
    - pwm: meson: Fix axg ao mux parents
    - pwm: meson: Fix g12a ao clk81 name
    - soundwire: qcom: correct setting ignore bit on v1.5.1
    - pinctrl: qcom: lpass-lpi: set output value before enabling output
    - ring-buffer: Sync IRQ works before buffer destruction
    - crypto: api - Demote BUG_ON() in crypto_unregister_alg() to a WARN_ON()
    - crypto: safexcel - Cleanup ring IRQ workqueues on load failure
    - rcu: Avoid stack overflow due to __rcu_irq_enter_check_tick() being kprobe-
      ed
    - reiserfs: Add security prefix to xattr name in reiserfs_security_write()
    - KVM: nVMX: Emulate NOPs in L2, and PAUSE if it's not intercepted
    - relayfs: fix out-of-bounds access in relay_file_read
    - writeback, cgroup: fix null-ptr-deref write in bdi_split_work_to_wbs
 ...

Changed in linux (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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: kernel-spammed-jammy-linux-aws-v2 verification-needed-jammy-linux-aws
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-linux-azure
Po-Hsu Lin (cypressyew)
summary: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events
- are caught" on J-5.15 P9 / J-kvm / L-kvm
+ are caught" on J-kvm / L-kvm
description: updated
Changed in linux (Ubuntu):
status: In Progress → Invalid
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws-5.15/5.15.0-1046.51~20.04.1 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-linux-aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'.

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: kernel-spammed-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-5.15
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-xilinx-zynqmp/5.15.0-1024.28 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-jammy-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'.

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: kernel-spammed-jammy-linux-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This issue is only affecting our KVM kernels, test passed on other kernels.

tags: added: verification-done-focal-linux-aws-5.15 verification-done-jammy-linux-aws verification-done-jammy-linux-azure verification-done-jammy-linux-xilinx-zynqmp
removed: verification-needed-focal-linux-aws-5.15 verification-needed-jammy-linux-aws verification-needed-jammy-linux-azure verification-needed-jammy-linux-xilinx-zynqmp
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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