syzbot


possible deadlock in v4l2_ctrl_handler_log_status

Status: upstream: reported C repro on 2024/02/08 09:17
Subsystems: media
[Documentation on labels]
Reported-by: syzbot+9948f8e188482c5d1a3e@syzkaller.appspotmail.com
First crash: 73d, last: 9m
Cause bisection: introduced by (bisect log) :
commit 9801b5b28c6929139d6fceeee8d739cc67bb2739
Author: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Date: Wed Jan 17 14:52:04 2024 +0000

  media: v4l2-ctrls: show all owned controls in log_status

Crash: possible deadlock in v4l2_ctrl_handler_log_status (log)
Repro: C syz .config
  
Discussions (2)
Title Replies (including bot) Last reply
[syzbot] Monthly media report (Apr 2024) 0 (1) 2024/04/13 14:40
[syzbot] [media?] possible deadlock in v4l2_ctrl_handler_log_status 1 (4) 2024/02/09 13:58
Last patch testing requests (2)
Created Duration User Patch Repo Result
2024/03/04 16:08 22m retest repro linux-next error OK
2024/02/09 08:11 21m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master OK log

Sample crash report:
vivid-001: =================  START STATUS  =================
vivid-001: Boolean: 
======================================================
WARNING: possible circular locking dependency detected
6.9.0-rc4-syzkaller-00164-gdbe0a7be2838 #0 Not tainted
------------------------------------------------------
syz-executor364/5079 is trying to acquire lock:
ffff888025bc06e0 (vivid_ctrls:1606:(hdl_user_gen)->_lock){+.+.}-{3:3}, at: v4l2_ctrl_lock include/media/v4l2-ctrls.h:572 [inline]
ffff888025bc06e0 (vivid_ctrls:1606:(hdl_user_gen)->_lock){+.+.}-{3:3}, at: log_ctrl drivers/media/v4l2-core/v4l2-ctrls-core.c:2519 [inline]
ffff888025bc06e0 (vivid_ctrls:1606:(hdl_user_gen)->_lock){+.+.}-{3:3}, at: v4l2_ctrl_handler_log_status+0x2f3/0x540 drivers/media/v4l2-core/v4l2-ctrls-core.c:2557

but task is already holding lock:
ffff888025bc24b0 (vivid_ctrls:1625:(hdl_vbi_cap)->_lock){+.+.}-{3:3}, at: v4l2_ctrl_handler_log_status+0x11f/0x540 drivers/media/v4l2-core/v4l2-ctrls-core.c:2552

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (vivid_ctrls:1625:(hdl_vbi_cap)->_lock){+.+.}-{3:3}:
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5754
       __mutex_lock_common kernel/locking/mutex.c:608 [inline]
       __mutex_lock+0x136/0xd70 kernel/locking/mutex.c:752
       find_ref_lock+0x5b/0x470 drivers/media/v4l2-core/v4l2-ctrls-core.c:1648
       handler_new_ref+0x102/0x940 drivers/media/v4l2-core/v4l2-ctrls-core.c:1685
       v4l2_ctrl_add_handler+0x1a1/0x290 drivers/media/v4l2-core/v4l2-ctrls-core.c:2209
       vivid_create_controls+0x27ab/0x3580 drivers/media/test-drivers/vivid/vivid-ctrls.c:1951
       vivid_create_instance drivers/media/test-drivers/vivid/vivid-core.c:1854 [inline]
       vivid_probe+0x4289/0x6fa0 drivers/media/test-drivers/vivid/vivid-core.c:2018
       platform_probe+0x13a/0x1c0 drivers/base/platform.c:1404
       really_probe+0x2b8/0xad0 drivers/base/dd.c:656
       __driver_probe_device+0x1a2/0x390 drivers/base/dd.c:798
       driver_probe_device+0x50/0x430 drivers/base/dd.c:828
       __driver_attach+0x45f/0x710 drivers/base/dd.c:1214
       bus_for_each_dev+0x239/0x2b0 drivers/base/bus.c:368
       bus_add_driver+0x347/0x620 drivers/base/bus.c:673
       driver_register+0x23a/0x320 drivers/base/driver.c:246
       vivid_init+0x3d/0x70 drivers/media/test-drivers/vivid/vivid-core.c:2145
       do_one_initcall+0x248/0x880 init/main.c:1243
       do_initcall_level+0x157/0x210 init/main.c:1305
       do_initcalls+0x3f/0x80 init/main.c:1321
       kernel_init_freeable+0x435/0x5d0 init/main.c:1553
       kernel_init+0x1d/0x2b0 init/main.c:1442
       ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

-> #0 (vivid_ctrls:1606:(hdl_user_gen)->_lock){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3134 [inline]
       check_prevs_add kernel/locking/lockdep.c:3253 [inline]
       validate_chain+0x18cb/0x58e0 kernel/locking/lockdep.c:3869
       __lock_acquire+0x1346/0x1fd0 kernel/locking/lockdep.c:5137
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5754
       __mutex_lock_common kernel/locking/mutex.c:608 [inline]
       __mutex_lock+0x136/0xd70 kernel/locking/mutex.c:752
       v4l2_ctrl_lock include/media/v4l2-ctrls.h:572 [inline]
       log_ctrl drivers/media/v4l2-core/v4l2-ctrls-core.c:2519 [inline]
       v4l2_ctrl_handler_log_status+0x2f3/0x540 drivers/media/v4l2-core/v4l2-ctrls-core.c:2557
       v4l2_ctrl_log_status+0xe3/0x100 drivers/media/v4l2-core/v4l2-ctrls-api.c:1206
       vidioc_log_status+0x63/0x110 drivers/media/test-drivers/vivid/vivid-core.c:426
       v4l_log_status+0x8f/0x110 drivers/media/v4l2-core/v4l2-ioctl.c:2562
       __video_do_ioctl+0xc26/0xde0 drivers/media/v4l2-core/v4l2-ioctl.c:3049
       video_usercopy+0x899/0x1180 drivers/media/v4l2-core/v4l2-ioctl.c:3390
       v4l2_ioctl+0x18c/0x1e0 drivers/media/v4l2-core/v4l2-dev.c:364
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:904 [inline]
       __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:890
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(vivid_ctrls:1625:(hdl_vbi_cap)->_lock);
                               lock(vivid_ctrls:1606:(hdl_user_gen)->_lock);
                               lock(vivid_ctrls:1625:(hdl_vbi_cap)->_lock);
  lock(vivid_ctrls:1606:(hdl_user_gen)->_lock);

 *** DEADLOCK ***

2 locks held by syz-executor364/5079:
 #0: ffff888025bc5aa8 (&dev->mutex#3){+.+.}-{3:3}, at: __video_do_ioctl+0x4ed/0xde0 drivers/media/v4l2-core/v4l2-ioctl.c:3017
 #1: ffff888025bc24b0 (vivid_ctrls:1625:(hdl_vbi_cap)->_lock){+.+.}-{3:3}, at: v4l2_ctrl_handler_log_status+0x11f/0x540 drivers/media/v4l2-core/v4l2-ctrls-core.c:2552

stack backtrace:
CPU: 1 PID: 5079 Comm: syz-executor364 Not tainted 6.9.0-rc4-syzkaller-00164-gdbe0a7be2838 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114
 check_noncircular+0x36a/0x4a0 kernel/locking/lockdep.c:2187
 check_prev_add kernel/locking/lockdep.c:3134 [inline]
 check_prevs_add kernel/locking/lockdep.c:3253 [inline]
 validate_chain+0x18cb/0x58e0 kernel/locking/lockdep.c:3869
 __lock_acquire+0x1346/0x1fd0 kernel/locking/lockdep.c:5137
 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5754
 __mutex_lock_common kernel/locking/mutex.c:608 [inline]
 __mutex_lock+0x136/0xd70 kernel/locking/mutex.c:752
 v4l2_ctrl_lock include/media/v4l2-ctrls.h:572 [inline]
 log_ctrl drivers/media/v4l2-core/v4l2-ctrls-core.c:2519 [inline]
 v4l2_ctrl_handler_log_status+0x2f3/0x540 drivers/media/v4l2-core/v4l2-ctrls-core.c:2557
 v4l2_ctrl_log_status+0xe3/0x100 drivers/media/v4l2-core/v4l2-ctrls-api.c:1206
 vidioc_log_status+0x63/0x110 drivers/media/test-drivers/vivid/vivid-core.c:426
 v4l_log_status+0x8f/0x110 drivers/media/v4l2-core/v4l2-ioctl.c:2562
 __video_do_ioctl+0xc26/0xde0 drivers/media/v4l2-core/v4l2-ioctl.c:3049
 video_usercopy+0x899/0x1180 drivers/media/v4l2-core/v4l2-ioctl.c:3390
 v4l2_ioctl+0x18c/0x1e0 drivers/media/v4l2-core/v4l2-dev.c:364
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:904 [inline]
 __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:890
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fda9eb1b0e9
Code: 48 83 c4 28 c3 e8 37 17 00 00 0f 1f 80 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff4f9beba8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fff4f9bed78 RCX: 00007fda9eb1b0e9
RDX: 0000000000000000 RSI: 0000000000005646 RDI: 0000000000000003
RBP: 00007fda9eb8e610 R08: 00236962762f7665 R09: 00007fff4f9bed78
R10: 000000000000001f R11: 0000000000000246 R12: 0000000000000001
R13: 00007fff4f9bed68 R14: 0000000000000001 R15: 0000000000000001
 </TASK>
true
vivid-001: Integer 32 Bits: 0
vivid-001: Integer 64 Bits: 0
vivid-001: Menu: Menu Item 3
vivid-001: String:   
vivid-001: Bitmask: 0x80002000
vivid-001: Integer Menu: 5
vivid-001: U32 1 Element Array: [1] 24
vivid-001: U16 8x16 Matrix: [8][16] 24
vivid-001: U8 2x3x4x5 Array: [2][3][4][5] 24
vivid-001: Area: unknown type 262
vivid-001: Read-Only Integer 32 Bits: 0
vivid-001: U32 Dynamic Array: [100] 50
vivid-001: U8 Pixel Array: [640][368] 128
vivid-001: S32 2 Element Array: [2] 2
vivid-001: S64 5 Element Array: [5] 4
vivid-001: Interlaced VBI Format: false
vivid-001: Loop Video: false
vivid-001: Wrap Sequence Number: false
vivid-001: Wr

Crashes (6638):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/20 04:22 upstream dbe0a7be2838 af24b050 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in v4l2_ctrl_handler_log_status
2024/04/13 12:26 linux-next 9ed46da14b9b c8349e48 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in v4l2_ctrl_handler_log_status
2024/02/08 08:06 linux-next b1d3a0e70c38 6404acf9 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/14 19:06 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci b5d2afe8745b c8349e48 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in v4l2_ctrl_handler_log_status
2024/04/21 07:54 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/21 07:16 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/21 06:51 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/21 06:50 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/21 05:50 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in v4l2_ctrl_handler_log_status
2024/04/21 05:29 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in v4l2_ctrl_handler_log_status
2024/04/21 04:28 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/21 03:52 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/21 03:15 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/21 03:13 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/21 02:12 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in v4l2_ctrl_handler_log_status
2024/04/21 01:36 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/21 01:27 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in v4l2_ctrl_handler_log_status
2024/04/21 00:26 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 23:22 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 22:06 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 21:12 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 20:37 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 19:22 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 18:00 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 17:27 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 17:12 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 17:07 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 16:04 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 16:02 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 14:55 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 13:06 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 13:04 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 12:00 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 11:38 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 11:38 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 10:28 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 08:19 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 07:31 upstream 13a2e429f644 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 06:45 upstream 3cdb45594619 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 04:13 upstream 3cdb45594619 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 03:46 upstream dbe0a7be2838 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 21:50 upstream 13a2e429f644 af24b050 .config console log report info [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 18:45 upstream 13a2e429f644 af24b050 .config console log report info [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 18:36 upstream 13a2e429f644 af24b050 .config console log report info [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 10:10 upstream 13a2e429f644 af24b050 .config console log report info [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in v4l2_ctrl_handler_log_status
2024/04/21 00:25 upstream 977b1ef51866 af24b050 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 06:10 upstream dbe0a7be2838 af24b050 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 06:09 upstream dbe0a7be2838 af24b050 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 23:06 upstream 977b1ef51866 af24b050 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in v4l2_ctrl_handler_log_status
2024/04/21 07:54 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/21 01:59 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 19:51 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 14:18 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 09:25 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 03:29 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in v4l2_ctrl_handler_log_status
2024/04/20 05:09 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 6a71d2909427 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in v4l2_ctrl_handler_log_status
* Struck through repros no longer work on HEAD.