syzbot


possible deadlock in attr_data_get_block (2)

Status: upstream: reported C repro on 2024/08/15 10:46
Subsystems: ntfs3
Labels: prio:high
[Documentation on labels]
Reported-by: syzbot+262a71e9d2faf8747085@syzkaller.appspotmail.com
First crash: 697d, last: 9h18m
Cause bisection: failed (error log, bisect log)
  
✨ AI Jobs (1)
ID Workflow Result Correct Bug Created Started Finished Revision Error
267c1761-b09a-427b-9769-fb6585b612e7 assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ✅ NetworkTrigger: ❌ PeripheralTrigger: ✅ RemoteTrigger: ❌ Unprivileged: ✅ UserNamespace: ✅ VMGuestTrigger: ❌ VMHostTrigger: ❌ possible deadlock in attr_data_get_block (2) 2026/05/26 03:55 2026/05/26 03:55 2026/05/26 04:43 c69befb30ac10e158cc9d1557b508ee3f0eca1de

			
		
Discussions (19)
Title Replies (including bot) Last reply
[PATCH 2/2] ntfs3: release ni_lock before dir_emit in ntfs_readdir to fix deadlocks 1 (1) 2026/07/01 01:30
[syzbot] Monthly ntfs3 report (Jun 2026) 0 (1) 2026/06/02 20:32
[syzbot] Monthly ntfs3 report (May 2026) 0 (1) 2026/05/02 12:32
[syzbot] Monthly ntfs3 report (Mar 2026) 0 (1) 2026/03/01 06:22
[syzbot] Monthly ntfs3 report (Jan 2026) 0 (1) 2026/01/28 22:39
[syzbot] Monthly ntfs3 report (Dec 2025) 0 (1) 2025/12/29 08:11
[syzbot] Monthly ntfs3 report (Nov 2025) 0 (1) 2025/11/27 07:44
[syzbot] Monthly ntfs3 report (Oct 2025) 0 (1) 2025/10/27 08:42
[syzbot] Monthly ntfs3 report (Sep 2025) 0 (1) 2025/09/25 16:00
[syzbot] Monthly ntfs3 report (Aug 2025) 0 (1) 2025/08/25 13:19
[syzbot] Monthly ntfs3 report (May 2025) 0 (1) 2025/05/24 10:04
[syzbot] Monthly ntfs3 report (Apr 2025) 0 (1) 2025/04/22 12:41
[syzbot] Monthly ntfs3 report (Mar 2025) 0 (1) 2025/03/18 14:49
[syzbot] Monthly ntfs3 report (Feb 2025) 0 (1) 2025/02/16 21:53
[syzbot] Monthly ntfs3 report (Jan 2025) 0 (1) 2025/01/15 08:54
[syzbot] Monthly ntfs3 report (Dec 2024) 0 (1) 2024/12/16 09:44
[syzbot] Monthly ntfs3 report (Nov 2024) 0 (1) 2024/11/13 11:07
[syzbot] Monthly ntfs3 report (Sep 2024) 0 (1) 2024/09/12 08:11
[syzbot] [ntfs3?] possible deadlock in attr_data_get_block (2) 0 (1) 2024/08/15 10:46
Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in attr_data_get_block origin:upstream missing-backport 4 C error 570 2d13h 1201d 0/3 upstream: reported C repro on 2023/03/29 04:32
linux-6.6 possible deadlock in attr_data_get_block origin:upstream missing-backport 4 C error 103 9d06h 379d 0/2 upstream: reported C repro on 2025/06/27 20:24
upstream possible deadlock in attr_data_get_block ntfs3 4 C error 3111 697d 1364d 27/29 fixed on 2024/08/14 03:44
linux-5.15 possible deadlock in attr_data_get_block origin:lts-only 4 C done 424 1d04h 1202d 0/3 upstream: reported C repro on 2023/03/27 15:11
Last patch testing requests (9)
Created Duration User Patch Repo Result
2026/05/16 18:23 38m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci OK log
2026/03/04 10:09 25m retest repro upstream OK log
2026/03/04 10:09 21m retest repro upstream OK log
2026/03/04 10:09 19m retest repro upstream OK log
2026/03/04 10:09 28m retest repro upstream OK log
2026/03/04 10:09 18m retest repro upstream OK log
2026/03/04 05:02 25m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci error
2026/03/04 04:52 25m retest repro upstream OK log
2026/03/04 04:42 26m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci error

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.9.1191/22318 is trying to acquire lock:
ffff88805e4172d8 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1222 [inline]
ffff88805e4172d8 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: attr_data_get_block+0x1bf/0x2a0 fs/ntfs3/attrib.c:976

but task is already holding lock:
ffff88805e417760 (mapping.invalidate_lock#7){.+.+}-{4:4}, at: filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline]
ffff88805e417760 (mapping.invalidate_lock#7){.+.+}-{4:4}, at: do_page_cache_ra mm/readahead.c:347 [inline]
ffff88805e417760 (mapping.invalidate_lock#7){.+.+}-{4:4}, at: page_cache_ra_order+0x2b1/0x4a0 mm/readahead.c:558

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (mapping.invalidate_lock#7){.+.+}-{4:4}:
       down_read+0x97/0x200 kernel/locking/rwsem.c:1574
       filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline]
       filemap_fault+0x6e0/0x13c0 mm/filemap.c:3570
       __do_fault+0x138/0x2a0 mm/memory.c:5425
       do_shared_fault mm/memory.c:5924 [inline]
       do_fault mm/memory.c:5998 [inline]
       do_pte_missing+0x659/0x28f0 mm/memory.c:4566
       handle_pte_fault mm/memory.c:6379 [inline]
       __handle_mm_fault mm/memory.c:6517 [inline]
       handle_mm_fault+0xd28/0x13f0 mm/memory.c:6686
       do_user_addr_fault+0x744/0x1340 arch/x86/mm/fault.c:1394
       handle_page_fault arch/x86/mm/fault.c:1483 [inline]
       exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1536
       asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:595
       stac arch/x86/include/asm/smap.h:-1 [inline]
       filldir64+0x29e/0x620 fs/readdir.c:365
       dir_emit include/linux/fs.h:3587 [inline]
       ntfs_dir_emit fs/ntfs3/dir.c:346 [inline]
       ntfs_read_hdr+0x8a4/0xc10 fs/ntfs3/dir.c:387
       ntfs_readdir+0x9ea/0xec0 fs/ntfs3/dir.c:547
       iterate_dir+0x2f1/0x4e0 fs/readdir.c:110
       __do_sys_getdents64 fs/readdir.c:399 [inline]
       __se_sys_getdents64+0xf1/0x280 fs/readdir.c:384
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&ni->ni_lock#2/5){+.+.}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3165 [inline]
       check_prevs_add kernel/locking/lockdep.c:3284 [inline]
       validate_chain kernel/locking/lockdep.c:3908 [inline]
       __lock_acquire+0x1520/0x2ce0 kernel/locking/lockdep.c:5237
       lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868
       __mutex_lock_common kernel/locking/rtmutex_api.c:559 [inline]
       mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:578
       ni_lock fs/ntfs3/ntfs_fs.h:1222 [inline]
       attr_data_get_block+0x1bf/0x2a0 fs/ntfs3/attrib.c:976
       ntfs_iomap_begin+0x4f0/0xf10 fs/ntfs3/inode.c:771
       iomap_iter+0x5f5/0xf80 fs/iomap/iter.c:110
       iomap_readahead+0xa4a/0xe80 fs/iomap/buffered-io.c:721
       ntfs_readahead+0x193/0x210 fs/ntfs3/inode.c:673
       read_pages+0x193/0x5a0 mm/readahead.c:174
       page_cache_ra_unbounded+0x679/0x8f0 mm/readahead.c:315
       do_page_cache_ra mm/readahead.c:348 [inline]
       page_cache_ra_order+0x2c1/0x4a0 mm/readahead.c:558
       filemap_get_pages+0x493/0x1e80 mm/filemap.c:2704
       filemap_read+0x429/0x11e0 mm/filemap.c:2814
       __kernel_read+0x4d3/0x970 fs/read_write.c:532
       integrity_kernel_read+0x89/0xd0 security/integrity/iint.c:28
       ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:222 [inline]
       ima_calc_file_hash+0x45d/0x8a0 security/integrity/ima/ima_crypto.c:280
       ima_collect_measurement+0x521/0xa10 security/integrity/ima/ima_api.c:300
       process_measurement+0x1282/0x1c20 security/integrity/ima/ima_main.c:425
       ima_file_check+0xe1/0x130 security/integrity/ima/ima_main.c:685
       security_file_post_open+0xb3/0x260 security/security.c:2755
       do_open fs/namei.c:4702 [inline]
       path_openat+0x2eac/0x3850 fs/namei.c:4863
       do_file_open+0x23e/0x4a0 fs/namei.c:4892
       do_sys_openat2+0x115/0x200 fs/open.c:1368
       do_sys_open fs/open.c:1374 [inline]
       __do_sys_openat fs/open.c:1390 [inline]
       __se_sys_openat fs/open.c:1385 [inline]
       __x64_sys_openat+0x138/0x170 fs/open.c:1385
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  rlock(mapping.invalidate_lock#7);
                               lock(&ni->ni_lock#2/5);
                               lock(mapping.invalidate_lock#7);
  lock(&ni->ni_lock#2/5);

 *** DEADLOCK ***

2 locks held by syz.9.1191/22318:
 #0: ffff888011fed158 (&ima_iint_mutex_key[depth]){+.+.}-{4:4}, at: process_measurement+0x7e0/0x1c20 security/integrity/ima/ima_main.c:319
 #1: ffff88805e417760 (mapping.invalidate_lock#7){.+.+}-{4:4}, at: filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline]
 #1: ffff88805e417760 (mapping.invalidate_lock#7){.+.+}-{4:4}, at: do_page_cache_ra mm/readahead.c:347 [inline]
 #1: ffff88805e417760 (mapping.invalidate_lock#7){.+.+}-{4:4}, at: page_cache_ra_order+0x2b1/0x4a0 mm/readahead.c:558

stack backtrace:
CPU: 0 UID: 0 PID: 22318 Comm: syz.9.1191 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_circular_bug+0x2e1/0x300 kernel/locking/lockdep.c:2043
 check_noncircular+0x12e/0x150 kernel/locking/lockdep.c:2175
 check_prev_add kernel/locking/lockdep.c:3165 [inline]
 check_prevs_add kernel/locking/lockdep.c:3284 [inline]
 validate_chain kernel/locking/lockdep.c:3908 [inline]
 __lock_acquire+0x1520/0x2ce0 kernel/locking/lockdep.c:5237
 lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868
 __mutex_lock_common kernel/locking/rtmutex_api.c:559 [inline]
 mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:578
 ni_lock fs/ntfs3/ntfs_fs.h:1222 [inline]
 attr_data_get_block+0x1bf/0x2a0 fs/ntfs3/attrib.c:976
 ntfs_iomap_begin+0x4f0/0xf10 fs/ntfs3/inode.c:771
 iomap_iter+0x5f5/0xf80 fs/iomap/iter.c:110
 iomap_readahead+0xa4a/0xe80 fs/iomap/buffered-io.c:721
 ntfs_readahead+0x193/0x210 fs/ntfs3/inode.c:673
 read_pages+0x193/0x5a0 mm/readahead.c:174
 page_cache_ra_unbounded+0x679/0x8f0 mm/readahead.c:315
 do_page_cache_ra mm/readahead.c:348 [inline]
 page_cache_ra_order+0x2c1/0x4a0 mm/readahead.c:558
 filemap_get_pages+0x493/0x1e80 mm/filemap.c:2704
 filemap_read+0x429/0x11e0 mm/filemap.c:2814
 __kernel_read+0x4d3/0x970 fs/read_write.c:532
 integrity_kernel_read+0x89/0xd0 security/integrity/iint.c:28
 ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:222 [inline]
 ima_calc_file_hash+0x45d/0x8a0 security/integrity/ima/ima_crypto.c:280
 ima_collect_measurement+0x521/0xa10 security/integrity/ima/ima_api.c:300
 process_measurement+0x1282/0x1c20 security/integrity/ima/ima_main.c:425
 ima_file_check+0xe1/0x130 security/integrity/ima/ima_main.c:685
 security_file_post_open+0xb3/0x260 security/security.c:2755
 do_open fs/namei.c:4702 [inline]
 path_openat+0x2eac/0x3850 fs/namei.c:4863
 do_file_open+0x23e/0x4a0 fs/namei.c:4892
 do_sys_openat2+0x115/0x200 fs/open.c:1368
 do_sys_open fs/open.c:1374 [inline]
 __do_sys_openat fs/open.c:1390 [inline]
 __se_sys_openat fs/open.c:1385 [inline]
 __x64_sys_openat+0x138/0x170 fs/open.c:1385
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f80cfbade59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f80cde06028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f80cfe35fa0 RCX: 00007f80cfbade59
RDX: 0000000000020542 RSI: 0000200000000040 RDI: ffffffffffffff9c
RBP: 00007f80cfc43e6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000015 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f80cfe36038 R14: 00007f80cfe35fa0 R15: 00007fff37612098
 </TASK>
ntfs3(loop9): ino=1e, "file1" attr_set_size_ex

Crashes (3739):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/07/11 23:17 upstream dd3210c47e8d d78ea535 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/10 23:57 upstream d96fcfe1b7f9 99e64375 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/10 12:23 upstream a635d6748234 4167ee25 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/10 10:05 upstream 2c7c88a412aa 4167ee25 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/07/08 14:51 upstream 0e35b9b6ec0f 88a4b44c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/08 12:06 upstream 0e35b9b6ec0f ab40da58 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in attr_data_get_block
2026/07/07 16:35 upstream 0e35b9b6ec0f 8e71ce95 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/07/07 06:45 upstream 0e35b9b6ec0f 8e71ce95 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in attr_data_get_block
2026/07/06 16:11 upstream 8cdeaa50eae8 88b240e4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/06 02:37 upstream f105f3631d51 fcece630 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/05 14:28 upstream 7404ce516372 fcece630 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/04 09:29 upstream 71dfdfb0209b fcece630 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/07/03 05:07 upstream 87320be9f0d2 58bf2096 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/07/01 13:29 upstream 665159e24674 00a5cf1c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/06/30 16:50 upstream dc59e4fea9d8 00e8b0fd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/06/30 12:44 upstream dc59e4fea9d8 fff8d0a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/06/28 06:17 upstream 780d569e6c4b fb92f11c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/06/26 14:21 upstream 4edcdefd4083 7ff32d8b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/06/26 11:44 upstream 4edcdefd4083 7ff32d8b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/06/26 00:29 upstream a142da0b2d32 7ff32d8b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/06/25 20:12 upstream a142da0b2d32 7ff32d8b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/06/25 18:02 upstream ab9de95c9cf9 432fd51a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/06/25 15:14 upstream ab9de95c9cf9 432fd51a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/06/25 08:35 upstream ab9de95c9cf9 cfa969bf .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/05/02 11:07 upstream f1a5e78a55eb a0d91488 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/04/16 16:30 upstream 1d51b370a0f8 321ae225 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/02/18 04:37 upstream c22e26bd0906 39751c21 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/02/17 18:29 upstream 970296997869 39751c21 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/02/17 16:33 upstream c22e26bd0906 06ec4f7b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/02/17 11:38 upstream c22e26bd0906 e439b951 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/02/17 08:21 upstream 970296997869 e439b951 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in attr_data_get_block
2026/02/17 04:37 upstream c22e26bd0906 e439b951 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/02/17 03:45 upstream c22e26bd0906 e439b951 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/02/17 01:46 upstream 57d76ceccee4 5d52cba5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/02/16 06:16 upstream c22e26bd0906 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/02/15 23:54 upstream c22e26bd0906 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/02/15 20:02 upstream c22e26bd0906 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/02/15 18:52 upstream bb7a3fc2c976 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/02/15 00:42 upstream ca4ee40bf13d 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in attr_data_get_block
2026/02/14 15:23 upstream c22e26bd0906 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/02/14 14:11 upstream c22e26bd0906 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/02/14 11:29 upstream 770aaedb461a 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in attr_data_get_block
2026/02/13 17:48 upstream cee73b1e840c 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/02/12 11:57 upstream c22e26bd0906 76a109e2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/02/11 03:25 upstream dc855b77719f 441e25b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in attr_data_get_block
2026/02/10 22:47 upstream 72c395024dac 91d776d3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/02/10 14:43 upstream 72c395024dac 91d776d3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in attr_data_get_block
2026/02/10 14:42 upstream 72c395024dac 91d776d3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in attr_data_get_block
2026/02/10 09:21 upstream 8a5203c630c6 4ab09a02 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/02/10 02:55 upstream 8a5203c630c6 4ab09a02 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in attr_data_get_block
2026/02/10 00:35 upstream 05f7e89ab973 4ab09a02 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in attr_data_get_block
2025/02/24 08:11 upstream d082ecbc71e9 d34966d1 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in attr_data_get_block
2024/09/13 10:33 upstream fdf042df0463 73e8a465 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in attr_data_get_block
2024/08/28 04:07 upstream 3ec3f5fc4a91 6c853ff9 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in attr_data_get_block
2024/08/28 02:49 upstream 3ec3f5fc4a91 6c853ff9 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-upstream-fs possible deadlock in attr_data_get_block
2024/08/15 01:11 upstream 9d5906799f7d e6b88e20 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in attr_data_get_block
2026/01/18 04:51 upstream 54e82e93ca93 d1b870e1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in attr_data_get_block
2025/11/18 06:04 upstream e7c375b18160 ef766cd7 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root possible deadlock in attr_data_get_block
2026/05/27 07:55 linux-next e7e28506af98 2b01f00e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in attr_data_get_block
2026/02/08 18:30 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 59e4d31a0470 4c131dc4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in attr_data_get_block
2025/10/11 19:54 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci bf45a62baffc ff1712fe .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 possible deadlock in attr_data_get_block
* Struck through repros no longer work on HEAD.