[v6.1] INFO: task hung in blkdev_fallocate

2 views

Skip to first unread message

syzbot

unread,

Mar 8, 2023, 12:38:48 AM3/8/23

to syzkaller...@googlegroups.com

Hello,

syzbot found the following issue on:

HEAD commit: 42616e0f09fb Linux 6.1.15
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1410806cc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=650737f7e9682672
dashboard link: https://syzkaller.appspot.com/bug?extid=dad55e856d8e05000edf
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f10713d1fd0f/disk-42616e0f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5a1307bb774e/vmlinux-42616e0f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/388238a30fe4/Image-42616e0f.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+dad55e...@syzkaller.appspotmail.com

INFO: task syz-executor.0:18623 blocked for more than 143 seconds.
Not tainted 6.1.15-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack:0 pid:18623 ppid:4337 flags:0x00000001
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5238 [inline]
__schedule+0xf84/0x1d54 kernel/sched/core.c:6551
schedule+0xc4/0x170 kernel/sched/core.c:6627
rwsem_down_write_slowpath+0xd60/0x161c kernel/locking/rwsem.c:1190
__down_write_common kernel/locking/rwsem.c:1305 [inline]
__down_write kernel/locking/rwsem.c:1314 [inline]
down_write+0x84/0x88 kernel/locking/rwsem.c:1563
filemap_invalidate_lock include/linux/fs.h:801 [inline]
blkdev_fallocate+0x1d4/0x340 block/fops.c:641
vfs_fallocate+0x478/0x5b4 fs/open.c:323
madvise_remove mm/madvise.c:991 [inline]
madvise_vma_behavior mm/madvise.c:1015 [inline]
madvise_walk_vmas mm/madvise.c:1250 [inline]
do_madvise+0x1724/0x2eb8 mm/madvise.c:1429
__do_sys_madvise mm/madvise.c:1442 [inline]
__se_sys_madvise mm/madvise.c:1440 [inline]
__arm64_sys_madvise+0xa4/0xc0 mm/madvise.c:1440
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffff800015915df0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcb4 kernel/rcu/tasks.h:507
1 lock held by rcu_tasks_trace/13:
#0: ffff8000159165f0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcb4 kernel/rcu/tasks.h:507
1 lock held by khungtaskd/28:
#0: ffff800015915c20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:303
1 lock held by klogd/3828:
2 locks held by getty/3991:
#0: ffff0000d431a098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001bbb02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1210 drivers/tty/n_tty.c:2177
3 locks held by kworker/u4:9/5750:
1 lock held by syz-executor.0/18616:
1 lock held by syz-executor.0/18623:
#0: ffff0000c04a9ed8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:801 [inline]
#0: ffff0000c04a9ed8 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x1d4/0x340 block/fops.c:641
1 lock held by syz-executor.4/18661:
#0: ffff0000c04a9ed8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
#0: ffff0000c04a9ed8 (mapping.invalidate_lock#2){++++}-{3:3}, at: page_cache_ra_unbounded+0xc8/0x6bc mm/readahead.c:226
1 lock held by syz-executor.4/18667:
#0: ffff0000c04a9ed8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:801 [inline]
#0: ffff0000c04a9ed8 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x1d4/0x340 block/fops.c:641
1 lock held by syz-executor.0/18684:
#0: ffff0000c04a9ed8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
#0: ffff0000c04a9ed8 (mapping.invalidate_lock#2){++++}-{3:3}, at: page_cache_ra_unbounded+0xc8/0x6bc mm/readahead.c:226
1 lock held by syz-executor.0/18685:
#0: ffff0000c04a9ed8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:801 [inline]
#0: ffff0000c04a9ed8 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x1d4/0x340 block/fops.c:641
1 lock held by syz-executor.0/18742:
#0: ffff0000c04a9ed8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
#0: ffff0000c04a9ed8 (mapping.invalidate_lock#2){++++}-{3:3}, at: page_cache_ra_unbounded+0xc8/0x6bc mm/readahead.c:226
1 lock held by syz-executor.0/18744:
#0: ffff0000c04a9ed8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:801 [inline]
#0: ffff0000c04a9ed8 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x1d4/0x340 block/fops.c:641

=============================================

---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,

Mar 12, 2023, 7:16:41 PM3/12/23

to syzkaller...@googlegroups.com

Hello,

syzbot found the following issue on:

HEAD commit: bbf9f29bac04 Linux 5.15.101
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12a07072c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=353a11a1dbfe7820
dashboard link: https://syzkaller.appspot.com/bug?extid=d1600ddb4950c2beebf5

compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:

disk image: https://storage.googleapis.com/syzbot-assets/741458b6f24d/disk-bbf9f29b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/46cdc0f15ae5/vmlinux-bbf9f29b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/15bf795c52fa/Image-bbf9f29b.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+d1600d...@syzkaller.appspotmail.com

INFO: task syz-executor.3:21688 blocked for more than 143 seconds.
Not tainted 5.15.101-syzkaller #0

"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz-executor.3 state:D stack: 0 pid:21688 ppid: 21672 flags:0x00000009
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0xfcc/0x1f1c kernel/sched/core.c:6369
schedule+0x11c/0x1c8 kernel/sched/core.c:6452
rwsem_down_write_slowpath+0xca8/0x1340 kernel/locking/rwsem.c:1157
__down_write_common kernel/locking/rwsem.c:1284 [inline]
__down_write kernel/locking/rwsem.c:1293 [inline]
down_write+0x25c/0x260 kernel/locking/rwsem.c:1542
filemap_invalidate_lock include/linux/fs.h:832 [inline]
blkdev_fallocate+0x208/0x378 block/fops.c:600
vfs_fallocate+0x478/0x5b4 fs/open.c:308
ksys_fallocate fs/open.c:331 [inline]
__do_sys_fallocate fs/open.c:339 [inline]
__se_sys_fallocate fs/open.c:337 [inline]
__arm64_sys_fallocate+0xc0/0x110 fs/open.c:337
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 <unknown>:584

Showing all locks held in the system:

1 lock held by khungtaskd/27:
#0: ffff800014b925a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:268
1 lock held by udevd/3584:
2 locks held by getty/3731:
#0: ffff0000d35f9098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff800018e902e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1200 drivers/tty/n_tty.c:2147
3 locks held by syz-executor.5/4097:
3 locks held by kworker/u4:12/8860:
1 lock held by syz-executor.3/21643:
1 lock held by syz-executor.3/21688:
#0: ffff0000c0566790 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:832 [inline]
#0: ffff0000c0566790 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x208/0x378 block/fops.c:600
1 lock held by syz-executor.3/21730:
#0: ffff0000c0566790 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:832 [inline]
#0: ffff0000c0566790 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x208/0x378 block/fops.c:600
2 locks held by syz-executor.3/21769:
1 lock held by syz-executor.0/23951:
#0: ffff800014b96a30 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x54/0x4b0 kernel/rcu/tree.c:3994

syzbot

unread,

Mar 12, 2023, 10:39:40 PM3/12/23

to syzkaller...@googlegroups.com

syzbot has found a reproducer for the following issue on:

HEAD commit: bbf9f29bac04 Linux 5.15.101
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=166a92dcc80000

kernel config: https://syzkaller.appspot.com/x/.config?x=353a11a1dbfe7820
dashboard link: https://syzkaller.appspot.com/bug?extid=d1600ddb4950c2beebf5
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17f9b634c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12631eecc80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/741458b6f24d/disk-bbf9f29b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/46cdc0f15ae5/vmlinux-bbf9f29b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/15bf795c52fa/Image-bbf9f29b.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d1600d...@syzkaller.appspotmail.com

INFO: task syz-executor202:4095 blocked for more than 143 seconds.

Not tainted 5.15.101-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz-executor202 state:D stack: 0 pid: 4095 ppid: 4093 flags:0x00000001

Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0xfcc/0x1f1c kernel/sched/core.c:6369
schedule+0x11c/0x1c8 kernel/sched/core.c:6452
rwsem_down_write_slowpath+0xca8/0x1340 kernel/locking/rwsem.c:1157
__down_write_common kernel/locking/rwsem.c:1284 [inline]
__down_write kernel/locking/rwsem.c:1293 [inline]
down_write+0x25c/0x260 kernel/locking/rwsem.c:1542
filemap_invalidate_lock include/linux/fs.h:832 [inline]
blkdev_fallocate+0x208/0x378 block/fops.c:600
vfs_fallocate+0x478/0x5b4 fs/open.c:308
ksys_fallocate fs/open.c:331 [inline]
__do_sys_fallocate fs/open.c:339 [inline]
__se_sys_fallocate fs/open.c:337 [inline]
__arm64_sys_fallocate+0xc0/0x110 fs/open.c:337
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 <unknown>:584

INFO: task syz-executor202:4097 blocked for more than 143 seconds.

Not tainted 5.15.101-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz-executor202 state:D stack: 0 pid: 4097 ppid: 4092 flags:0x00000001

INFO: task syz-executor202:4098 blocked for more than 143 seconds.

Not tainted 5.15.101-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz-executor202 state:D stack: 0 pid: 4098 ppid: 4089 flags:0x00000001

INFO: task syz-executor202:4099 blocked for more than 143 seconds.

Not tainted 5.15.101-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz-executor202 state:D stack: 0 pid: 4099 ppid: 4091 flags:0x00000001

1 lock held by klogd/3575:
2 locks held by getty/3734:
#0: ffff0000d3cb9098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340

#1: ffff800018e902e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1200 drivers/tty/n_tty.c:2147

1 lock held by syz-executor202/4095:
#0: ffff0000c04b7350 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:832 [inline]
#0: ffff0000c04b7350 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x208/0x378 block/fops.c:600
1 lock held by syz-executor202/4096:
1 lock held by syz-executor202/4097:
#0: ffff0000c04b7350 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:832 [inline]
#0: ffff0000c04b7350 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x208/0x378 block/fops.c:600
1 lock held by syz-executor202/4098:
#0: ffff0000c04b7350 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:832 [inline]
#0: ffff0000c04b7350 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x208/0x378 block/fops.c:600
1 lock held by syz-executor202/4099:
#0: ffff0000c04b7350 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:832 [inline]
#0: ffff0000c04b7350 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x208/0x378 block/fops.c:600
1 lock held by syz-executor202/4106:
#0: ffff0000c04b7350 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:832 [inline]
#0: ffff0000c04b7350 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x208/0x378 block/fops.c:600

=============================================

syzbot

unread,

Mar 13, 2023, 12:06:58 AM3/13/23

to syzkaller...@googlegroups.com

syzbot has found a reproducer for the following issue on:

HEAD commit: 1cc3fcf63192 Linux 6.1.18
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10db9724c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=157296d36f92ea19

dashboard link: https://syzkaller.appspot.com/bug?extid=dad55e856d8e05000edf
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16607072c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17584f66c80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0e4c0d43698b/disk-1cc3fcf6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a4de39d735de/vmlinux-1cc3fcf6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/82bab928f6e3/Image-1cc3fcf6.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+dad55e...@syzkaller.appspotmail.com

INFO: task syz-executor747:4350 blocked for more than 143 seconds.
Not tainted 6.1.18-syzkaller #0

"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz-executor747 state:D stack:0 pid:4350 ppid:4348 flags:0x00000001

Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5238 [inline]

__schedule+0xf9c/0x1d84 kernel/sched/core.c:6551
schedule+0xc4/0x170 kernel/sched/core.c:6627
rwsem_down_write_slowpath+0xc80/0x156c kernel/locking/rwsem.c:1189
__down_write_common kernel/locking/rwsem.c:1314 [inline]
__down_write kernel/locking/rwsem.c:1323 [inline]
down_write+0x84/0x88 kernel/locking/rwsem.c:1574
filemap_invalidate_lock include/linux/fs.h:801 [inline]
blkdev_fallocate+0x1d4/0x340 block/fops.c:656
vfs_fallocate+0x478/0x5b4 fs/open.c:323
ksys_fallocate fs/open.c:346 [inline]
__do_sys_fallocate fs/open.c:354 [inline]
__se_sys_fallocate fs/open.c:352 [inline]
__arm64_sys_fallocate+0xc0/0x110 fs/open.c:352

__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581

INFO: task syz-executor747:4353 blocked for more than 143 seconds.
Not tainted 6.1.18-syzkaller #0

"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz-executor747 state:D stack:0 pid:4353 ppid:4347 flags:0x00000001

Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5238 [inline]

INFO: task syz-executor747:4354 blocked for more than 143 seconds.
Not tainted 6.1.18-syzkaller #0

"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz-executor747 state:D stack:0 pid:4354 ppid:4344 flags:0x00000001

Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5238 [inline]

#0: ffff800015905db0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:510

1 lock held by rcu_tasks_trace/13:

#0: ffff8000159065b0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:510

1 lock held by khungtaskd/28:

#0: ffff800015905be0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:305

1 lock held by klogd/3828:

2 locks held by getty/3994:
#0: ffff0000d3f2a098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001bbc02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1210 drivers/tty/n_tty.c:2177
1 lock held by syz-executor747/4350:
#0: ffff0000c05493d8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:801 [inline]
#0: ffff0000c05493d8 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x1d4/0x340 block/fops.c:656
1 lock held by syz-executor747/4352:
1 lock held by syz-executor747/4353:
#0: ffff0000c05493d8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:801 [inline]
#0: ffff0000c05493d8 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x1d4/0x340 block/fops.c:656
1 lock held by syz-executor747/4354:
#0: ffff0000c05493d8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:801 [inline]
#0: ffff0000c05493d8 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x1d4/0x340 block/fops.c:656
1 lock held by syz-executor747/4356:
#0: ffff0000c05493d8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:801 [inline]
#0: ffff0000c05493d8 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x1d4/0x340 block/fops.c:656
1 lock held by syz-executor747/4363:
#0: ffff0000c05493d8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:801 [inline]
#0: ffff0000c05493d8 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x1d4/0x340 block/fops.c:656

=============================================

Reply all

Reply to author

Forward

0 new messages