syzbot


possible deadlock in gup_fast_fallback

Status: upstream: reported C repro on 2024/04/21 03:14
Subsystems: mm
[Documentation on labels]
Reported-by: syzbot+63ba90b81c16b86379bd@syzkaller.appspotmail.com
First crash: 301d, last: 25m
Cause bisection: introduced by (bisect log) :
commit 69505fe98f198ee813898cbcaf6770949636430b
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Thu May 30 07:54:07 2024 +0000

  fs/ntfs3: Replace inode_trylock with inode_lock

Crash: possible deadlock in gup_fast_fallback (log)
Repro: C syz .config
  
Discussions (7)
Title Replies (including bot) Last reply
[syzbot] Monthly mm report (Feb 2025) 0 (1) 2025/02/05 12:44
[syzbot] Monthly mm report (Jan 2025) 0 (1) 2025/01/06 10:01
[syzbot] Monthly mm report (Dec 2024) 0 (1) 2024/12/05 09:04
[syzbot] Monthly mm report (Nov 2024) 1 (2) 2024/11/04 12:58
[syzbot] Monthly mm report (Oct 2024) 0 (1) 2024/10/03 09:02
[syzbot] Monthly mm report (Sep 2024) 0 (1) 2024/09/02 08:17
[syzbot] [mm?] possible deadlock in gup_fast_fallback 0 (3) 2024/07/25 01:01

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.12.0-syzkaller-11677-g2ba9f676d0a2 #0 Not tainted
------------------------------------------------------
syz-executor331/5818 is trying to acquire lock:
ffff88807b8fbae0 (&mm->mmap_lock){++++}-{4:4}, at: gup_fast_fallback+0x230/0x2b80 mm/gup.c:3407

but task is already holding lock:
ffff888071d18398 (&sb->s_type->i_mutex_key#14){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:818 [inline]
ffff888071d18398 (&sb->s_type->i_mutex_key#14){+.+.}-{4:4}, at: __blockdev_direct_IO+0x31d/0x4890 fs/direct-io.c:1140

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&sb->s_type->i_mutex_key#14){+.+.}-{4:4}:
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849
       down_write+0x99/0x220 kernel/locking/rwsem.c:1577
       inode_lock include/linux/fs.h:818 [inline]
       ntfs_file_mmap+0x5bc/0x850 fs/ntfs3/file.c:379
       call_mmap include/linux/fs.h:2183 [inline]
       mmap_file mm/internal.h:124 [inline]
       __mmap_new_file_vma mm/vma.c:2291 [inline]
       __mmap_new_vma mm/vma.c:2355 [inline]
       __mmap_region+0x2204/0x2cd0 mm/vma.c:2456
       mmap_region+0x226/0x2c0 mm/mmap.c:1347
       do_mmap+0x8f0/0x1000 mm/mmap.c:496
       vm_mmap_pgoff+0x1dd/0x3d0 mm/util.c:580
       ksys_mmap_pgoff+0x4eb/0x720 mm/mmap.c:542
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&mm->mmap_lock){++++}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3161 [inline]
       check_prevs_add kernel/locking/lockdep.c:3280 [inline]
       validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3904
       __lock_acquire+0x1397/0x2100 kernel/locking/lockdep.c:5226
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849
       gup_fast_fallback+0x249/0x2b80 mm/gup.c:3407
       pin_user_pages_fast+0xcc/0x160 mm/gup.c:3531
       iov_iter_extract_user_pages lib/iov_iter.c:1844 [inline]
       iov_iter_extract_pages+0x3bb/0x5c0 lib/iov_iter.c:1907
       dio_refill_pages fs/direct-io.c:172 [inline]
       dio_get_page fs/direct-io.c:213 [inline]
       do_direct_IO fs/direct-io.c:915 [inline]
       __blockdev_direct_IO+0x1443/0x4890 fs/direct-io.c:1243
       blockdev_direct_IO include/linux/fs.h:3313 [inline]
       ntfs_direct_IO+0x194/0x370 fs/ntfs3/inode.c:806
       generic_file_read_iter+0x341/0x550 mm/filemap.c:2811
       new_sync_read fs/read_write.c:484 [inline]
       vfs_read+0x991/0xb70 fs/read_write.c:565
       ksys_read+0x18f/0x2b0 fs/read_write.c:708
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xf3/0x230 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(&sb->s_type->i_mutex_key#14);
                               lock(&mm->mmap_lock);
                               lock(&sb->s_type->i_mutex_key#14);
  rlock(&mm->mmap_lock);

 *** DEADLOCK ***

1 lock held by syz-executor331/5818:
 #0: ffff888071d18398 (&sb->s_type->i_mutex_key#14){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:818 [inline]
 #0: ffff888071d18398 (&sb->s_type->i_mutex_key#14){+.+.}-{4:4}, at: __blockdev_direct_IO+0x31d/0x4890 fs/direct-io.c:1140

stack backtrace:
CPU: 1 UID: 0 PID: 5818 Comm: syz-executor331 Not tainted 6.12.0-syzkaller-11677-g2ba9f676d0a2 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 print_circular_bug+0x13a/0x1b0 kernel/locking/lockdep.c:2074
 check_noncircular+0x36a/0x4a0 kernel/locking/lockdep.c:2206
 check_prev_add kernel/locking/lockdep.c:3161 [inline]
 check_prevs_add kernel/locking/lockdep.c:3280 [inline]
 validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3904
 __lock_acquire+0x1397/0x2100 kernel/locking/lockdep.c:5226
 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849
 gup_fast_fallback+0x249/0x2b80 mm/gup.c:3407
 pin_user_pages_fast+0xcc/0x160 mm/gup.c:3531
 iov_iter_extract_user_pages lib/iov_iter.c:1844 [inline]
 iov_iter_extract_pages+0x3bb/0x5c0 lib/iov_iter.c:1907
 dio_refill_pages fs/direct-io.c:172 [inline]
 dio_get_page fs/direct-io.c:213 [inline]
 do_direct_IO fs/direct-io.c:915 [inline]
 __blockdev_direct_IO+0x1443/0x4890 fs/direct-io.c:1243
 blockdev_direct_IO include/linux/fs.h:3313 [inline]
 ntfs_direct_IO+0x194/0x370 fs/ntfs3/inode.c:806
 generic_file_read_iter+0x341/0x550 mm/filemap.c:2811
 new_sync_read fs/read_write.c:484 [inline]
 vfs_read+0x991/0xb70 fs/read_write.c:565
 ksys_read+0x18f/0x2b0 fs/read_write.c:708
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f77d867ed59
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 17 00 00 90 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:00007fffb251d198 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 0031656c69662f2e RCX: 00007f77d867ed59
RDX: 0000000000002000 RSI: 0000000020000000 RDI: 0000000000000006
RBP: 0000000000000000 R08: 00005555861fd4c0 R09: 00005555861fd4c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fffb251d1c0
R13: 00007fffb251d3e8 R14: 431bde82d7b634db R15: 00007f77d86c803b
 </TASK>

Crashes (1490):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/12/01 01:30 upstream 2ba9f676d0a2 68914665 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-upstream-fs possible deadlock in gup_fast_fallback
2024/07/24 14:09 upstream 786c8248dbd3 57b2edb1 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/12 05:07 upstream 09fbf3d50205 f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/12 02:47 upstream 09fbf3d50205 f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/11 01:46 upstream a64dcfb451e2 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/10 14:53 upstream a64dcfb451e2 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in gup_fast_fallback
2025/02/10 12:32 upstream a64dcfb451e2 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/10 06:37 upstream 69b54314c975 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/10 02:42 upstream a64dcfb451e2 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in gup_fast_fallback
2025/02/10 02:42 upstream a64dcfb451e2 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in gup_fast_fallback
2025/02/09 11:08 upstream 9946eaf552b1 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/08 17:50 upstream 8f6629c004b1 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/08 09:22 upstream 7ee983c850b4 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/07 19:19 upstream bb066fe812d6 53657d1b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/06 09:30 upstream 92514ef226f5 577d049b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/06 04:35 upstream 92514ef226f5 577d049b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/05 09:34 upstream 5c8c229261f1 5896748e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in gup_fast_fallback
2025/02/05 03:08 upstream d009de7d5428 5896748e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/04 20:17 upstream d009de7d5428 8f267cef .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/04 13:46 upstream 0de63bb7d919 8f267cef .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/04 12:07 upstream 0de63bb7d919 8f267cef .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/04 08:45 upstream 0de63bb7d919 8f267cef .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/04 06:46 upstream 0de63bb7d919 8f267cef .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/04 04:15 upstream 0de63bb7d919 a21a8419 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in gup_fast_fallback
2025/02/04 02:26 upstream 0de63bb7d919 8f267cef .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/04 00:40 upstream 2014c95afece a21a8419 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in gup_fast_fallback
2025/02/03 20:06 upstream 2014c95afece a21a8419 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/03 14:27 upstream 2014c95afece a21a8419 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in gup_fast_fallback
2025/02/03 11:57 upstream 2014c95afece a21a8419 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/03 07:36 upstream 69b8923f5003 568559e4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/03 06:41 upstream 69b8923f5003 568559e4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/02 15:37 upstream 69b8923f5003 568559e4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/02 14:12 upstream 69b8923f5003 568559e4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/02 12:23 upstream 69b8923f5003 568559e4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/02 08:30 upstream 69b8923f5003 568559e4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/02 02:39 upstream 69b8923f5003 568559e4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/02/01 23:14 upstream 69b8923f5003 568559e4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in gup_fast_fallback
2025/01/31 18:05 upstream 69e858e0b8b2 aa47157c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in gup_fast_fallback
2025/01/27 11:10 upstream 9c5968db9e62 9fbd772e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in gup_fast_fallback
2025/01/25 06:16 upstream 47d65738b975 9fbd772e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in gup_fast_fallback
2025/01/24 10:53 upstream 21266b8df522 521b0ce3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in gup_fast_fallback
2025/01/23 09:54 upstream 7004a2e46d16 9d4f14f8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in gup_fast_fallback
2025/02/08 12:08 upstream 7ee983c850b4 ef44b750 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in gup_fast_fallback
2025/01/28 02:32 upstream 805ba04cb7cc 18070896 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in gup_fast_fallback
2025/01/25 17:37 upstream b46c89c08f41 9fbd772e .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in gup_fast_fallback
2025/01/16 14:13 upstream 619f0b6fad52 f9e07a6e .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in gup_fast_fallback
2024/12/18 16:33 upstream aef25be35d23 1432fc84 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in gup_fast_fallback
2025/02/07 06:51 linux-next ed58d103e6da 53657d1b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in gup_fast_fallback
2024/04/17 03:03 linux-next 66e4190e92ce 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in gup_fast_fallback
2025/02/11 15:03 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2014c95afece f2baddf5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in gup_fast_fallback
2025/02/11 04:10 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2014c95afece 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in gup_fast_fallback
2025/02/08 20:33 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2014c95afece ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in gup_fast_fallback
2025/02/02 21:43 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 1950a0af2d55 568559e4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in gup_fast_fallback
2025/02/02 01:29 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 1950a0af2d55 0dff8567 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in gup_fast_fallback
2025/02/01 18:25 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 1950a0af2d55 0dff8567 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in gup_fast_fallback
2025/01/30 05:04 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 1950a0af2d55 afe4eff5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in gup_fast_fallback
2025/01/29 21:59 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 1950a0af2d55 afe4eff5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in gup_fast_fallback
2025/01/28 22:09 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 1950a0af2d55 f5427d7c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in gup_fast_fallback
2025/01/28 05:09 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 1950a0af2d55 18070896 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in gup_fast_fallback
2025/01/27 14:24 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 1950a0af2d55 9fbd772e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in gup_fast_fallback
* Struck through repros no longer work on HEAD.