INFO: task hung in invalidate_inode_pages2_range

36 views
Skip to first unread message

syzbot

unread,
Dec 23, 2017, 2:26:02 AM12/23/17
to ak...@linux-foundation.org, ja...@suse.cz, jla...@redhat.com, linux-...@vger.kernel.org, linu...@kvack.org, mgo...@techsingularity.net, npi...@gmail.com, rgol...@suse.com, syzkall...@googlegroups.com, vi...@zeniv.linux.org.uk
Hello,

syzkaller hit the following crash on
0e08c463db387a2adcb0243b15ab868a73f87807
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.

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


INFO: task syz-executor5:23726 blocked for more than 120 seconds.
Not tainted 4.15.0-rc4-next-20171221+ #78
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor5 D23744 23726 3376 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2800 [inline]
__schedule+0x8eb/0x2060 kernel/sched/core.c:3376
schedule+0xf5/0x430 kernel/sched/core.c:3435
io_schedule+0x1c/0x70 kernel/sched/core.c:5043
wait_on_page_bit_common mm/filemap.c:1099 [inline]
__lock_page+0x574/0x720 mm/filemap.c:1272
lock_page include/linux/pagemap.h:483 [inline]
invalidate_inode_pages2_range+0x995/0x1180 mm/truncate.c:702
generic_file_direct_write+0x184/0x440 mm/filemap.c:3029
__generic_file_write_iter+0x21f/0x5b0 mm/filemap.c:3220
blkdev_write_iter+0x207/0x3e0 fs/block_dev.c:1893
call_write_iter include/linux/fs.h:1776 [inline]
do_iter_readv_writev+0x525/0x7f0 fs/read_write.c:653
do_iter_write+0x154/0x540 fs/read_write.c:932
vfs_iter_write+0x77/0xb0 fs/read_write.c:945
iter_file_splice_write+0x7db/0xf30 fs/splice.c:749
do_splice_from fs/splice.c:851 [inline]
direct_splice_actor+0x125/0x180 fs/splice.c:1018
splice_direct_to_actor+0x2c1/0x820 fs/splice.c:973
do_splice_direct+0x29b/0x3c0 fs/splice.c:1061
do_sendfile+0x5c9/0xe80 fs/read_write.c:1413
SYSC_sendfile64 fs/read_write.c:1468 [inline]
SyS_sendfile64+0xbd/0x160 fs/read_write.c:1460
entry_SYSCALL_64_fastpath+0x1f/0x96
RIP: 0033:0x452a09
RSP: 002b:00007fa16f894c58 EFLAGS: 00000212 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007fa16f895700 RCX: 0000000000452a09
RDX: 00000000200ddff8 RSI: 0000000000000014 RDI: 0000000000000013
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000100000001 R11: 0000000000000212 R12: 0000000000000000
R13: 0000000000a2f7ff R14: 00007fa16f8959c0 R15: 0000000000000000

Showing all locks held in the system:
2 locks held by khungtaskd/676:
#0: (rcu_read_lock){....}, at: [<000000007f24b127>]
check_hung_uninterruptible_tasks kernel/hung_task.c:175 [inline]
#0: (rcu_read_lock){....}, at: [<000000007f24b127>] watchdog+0x1c5/0xd60
kernel/hung_task.c:249
#1: (tasklist_lock){.+.+}, at: [<000000003bf61d5e>]
debug_show_all_locks+0xd3/0x400 kernel/locking/lockdep.c:4464
2 locks held by getty/3115:
#0: (&tty->ldisc_sem){++++}, at: [<00000000d9b2bc58>]
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
#1: (&ldata->atomic_read_lock){+.+.}, at: [<000000004bd14182>]
n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
2 locks held by getty/3116:
#0: (&tty->ldisc_sem){++++}, at: [<00000000d9b2bc58>]
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
#1: (&ldata->atomic_read_lock){+.+.}, at: [<000000004bd14182>]
n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
2 locks held by getty/3117:
#0: (&tty->ldisc_sem){++++}, at: [<00000000d9b2bc58>]
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
#1: (&ldata->atomic_read_lock){+.+.}, at: [<000000004bd14182>]
n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
2 locks held by getty/3118:
#0: (&tty->ldisc_sem){++++}, at: [<00000000d9b2bc58>]
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
#1: (&ldata->atomic_read_lock){+.+.}, at: [<000000004bd14182>]
n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
2 locks held by getty/3119:
#0: (&tty->ldisc_sem){++++}, at: [<00000000d9b2bc58>]
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
#1: (&ldata->atomic_read_lock){+.+.}, at: [<000000004bd14182>]
n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
2 locks held by getty/3120:
#0: (&tty->ldisc_sem){++++}, at: [<00000000d9b2bc58>]
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
#1: (&ldata->atomic_read_lock){+.+.}, at: [<000000004bd14182>]
n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
2 locks held by getty/3121:
#0: (&tty->ldisc_sem){++++}, at: [<00000000d9b2bc58>]
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
#1: (&ldata->atomic_read_lock){+.+.}, at: [<000000004bd14182>]
n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
1 lock held by blkid/22055:
#0: (&bdev->bd_mutex){+.+.}, at: [<00000000834eac5c>]
__blkdev_put+0xbc/0x7f0 fs/block_dev.c:1757

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

NMI backtrace for cpu 1
CPU: 1 PID: 676 Comm: khungtaskd Not tainted 4.15.0-rc4-next-20171221+ #78
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x194/0x257 lib/dump_stack.c:53
nmi_cpu_backtrace+0x1d2/0x210 lib/nmi_backtrace.c:103
nmi_trigger_cpumask_backtrace+0x122/0x180 lib/nmi_backtrace.c:62
arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38
trigger_all_cpu_backtrace include/linux/nmi.h:138 [inline]
check_hung_task kernel/hung_task.c:132 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:190 [inline]
watchdog+0x90c/0xd60 kernel/hung_task.c:249
kthread+0x33c/0x400 kernel/kthread.c:238
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:524
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-rc4-next-20171221+ #78
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:raise_softirq_irqoff+0x271/0x320 kernel/softirq.c:430
RSP: 0018:ffff8801db207c90 EFLAGS: 00000046
RAX: 0000000000000001 RBX: 1ffff1003b640f93 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 1ffff1003b640fc5 RDI: ffffffff8642cbb4
RBP: ffff8801db207d60 R08: 1ffff1003b645a5d R09: ffff88021fff8008
R10: ffff88021fff8010 R11: ffff88021fff801d R12: 0000000000000007
R13: ffff8801db207d38 R14: ffff8801db207e68 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8801db200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000001c32000 CR3: 0000000006422002 CR4: 00000000001606f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
scheduler_ipi+0x50b/0x820 kernel/sched/core.c:1802
smp_reschedule_interrupt+0xe6/0x670 arch/x86/kernel/smp.c:277
reschedule_interrupt+0xa9/0xb0 arch/x86/entry/entry_64.S:944
</IRQ>
RIP: 0010:native_safe_halt+0x6/0x10 arch/x86/include/asm/irqflags.h:54
RSP: 0018:ffffffff86407c38 EFLAGS: 00000286 ORIG_RAX: ffffffffffffff02
RAX: dffffc0000000000 RBX: 1ffffffff0c80f8a RCX: 0000000000000000
RDX: 1ffffffff0c990a8 RSI: 0000000000000001 RDI: ffffffff864c8540
RBP: ffffffff86407c38 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: ffffffff86407cf0 R14: ffffffff86be46e0 R15: 0000000000000000
arch_safe_halt arch/x86/include/asm/paravirt.h:93 [inline]
default_idle+0xbf/0x430 arch/x86/kernel/process.c:354
arch_cpu_idle+0xa/0x10 arch/x86/kernel/process.c:345
default_idle_call+0x36/0x90 kernel/sched/idle.c:98
cpuidle_idle_call kernel/sched/idle.c:156 [inline]
do_idle+0x24a/0x3b0 kernel/sched/idle.c:246
cpu_startup_entry+0x104/0x120 kernel/sched/idle.c:351
rest_init+0xed/0xf0 init/main.c:436
start_kernel+0x7f1/0x819 init/main.c:716
x86_64_start_reservations+0x2a/0x2c arch/x86/kernel/head64.c:378
x86_64_start_kernel+0x77/0x7a arch/x86/kernel/head64.c:359
secondary_startup_64+0xa5/0xb0 arch/x86/kernel/head_64.S:237
Code: e8 b5 80 19 00 85 c0 74 09 80 3d 71 de 78 05 00 74 19 65 ff 0d d1 c2
be 7e e9 2e fe ff ff 4c 89 e7 e8 a4 f6 09 00 e9 7c fe ff ff <e8> 2a 82 19
00 85 c0 75 de 48 c7 c2 c0 dc 88 85 be a1 00 00 00


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.
Please credit me with: Reported-by: syzbot <syzk...@googlegroups.com>

syzbot will keep track of this bug report.
Once a fix for this bug is merged into any tree, reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.
config.txt
raw.log

syzbot

unread,
Feb 22, 2019, 5:34:21 AM2/22/19
to syzkall...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages