WARNING in __mark_inode_dirty

8 views
Skip to first unread message

syzbot

unread,
Apr 12, 2019, 8:01:27 PM4/12/19
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 666c420f FROMLIST: ANDROID: binder: Add BINDER_GET_NODE_IN..
git tree: android-4.14
console output: https://syzkaller.appspot.com/x/log.txt?x=1709f276400000
kernel config: https://syzkaller.appspot.com/x/.config?x=89d929f317ea847c
dashboard link: https://syzkaller.appspot.com/bug?extid=29f0282f64e6d503d460
compiler: gcc (GCC) 8.0.1 20180413 (experimental)

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

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

audit: type=1400 audit(1537730742.459:47): avc: denied { getopt } for
pid=18604 comm="syz-executor3"
scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023
tcontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023
tclass=netlink_fib_lookup_socket permissive=1
bdi-block not registered
------------[ cut here ]------------
WARNING: CPU: 0 PID: 18579 at fs/fs-writeback.c:2162
__mark_inode_dirty.cold.12+0x15/0x2a fs/fs-writeback.c:2160
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 18579 Comm: syz-executor5 Not tainted 4.14.71+ #8
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0xb9/0x11b lib/dump_stack.c:53
panic+0x1bf/0x3a4 kernel/panic.c:181
__warn.cold.7+0x148/0x185 kernel/panic.c:542
report_bug+0x1f7/0x26c lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
do_error_trap+0x1ba/0x2c0 arch/x86/kernel/traps.c:295
invalid_op+0x18/0x40 arch/x86/entry/entry_64.S:944
RIP: 0010:__mark_inode_dirty.cold.12+0x15/0x2a fs/fs-writeback.c:2160
RSP: 0018:ffff8801ca787478 EFLAGS: 00010282
RAX: 0000000000000018 RBX: ffff8801da412f98 RCX: 0000000000013f2e
RDX: 0000000000000000 RSI: ffffc90001b7c000 RDI: ffffffffb7bce3a0
RBP: ffff8801a58f0000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8801a58f0058
R13: ffff8801da413070 R14: ffff8801a58f00b0 R15: ffff8801a58f0000
mark_buffer_dirty+0x24f/0x480 fs/buffer.c:1176
__block_commit_write.isra.12+0x13d/0x210 fs/buffer.c:2099
block_write_end+0x42/0xf0 fs/buffer.c:2177
blkdev_write_end+0x3c/0x110 fs/block_dev.c:606
generic_perform_write+0x294/0x430 mm/filemap.c:3048
__generic_file_write_iter+0x345/0x540 mm/filemap.c:3162
blkdev_write_iter+0x1fa/0x3d0 fs/block_dev.c:1906
call_write_iter include/linux/fs.h:1782 [inline]
do_iter_readv_writev+0x3a4/0x560 fs/read_write.c:678
do_iter_write+0x156/0x530 fs/read_write.c:957
vfs_iter_write+0x70/0xa0 fs/read_write.c:970
iter_file_splice_write+0x5b4/0xab0 fs/splice.c:749
do_splice_from fs/splice.c:851 [inline]
direct_splice_actor+0x116/0x160 fs/splice.c:1018
splice_direct_to_actor+0x28c/0x750 fs/splice.c:973
do_splice_direct+0x17b/0x220 fs/splice.c:1061
do_sendfile+0x4a1/0xb50 fs/read_write.c:1438
SYSC_sendfile64 fs/read_write.c:1493 [inline]
SyS_sendfile64+0xab/0x140 fs/read_write.c:1485
do_syscall_64+0x19b/0x4b0 arch/x86/entry/common.c:289
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x457679
RSP: 002b:00007f461a435c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007f461a4366d4 RCX: 0000000000457679
RDX: 0000000020000000 RSI: 0000000000000007 RDI: 0000000000000007
RBP: 000000000072bfa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000002000005 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000004d5428 R14: 00000000004c35e5 R15: 0000000000000001
Kernel Offset: 0x33200000 from 0xffffffff81000000 (relocation range:
0xffffffff80000000-0xffffffffbfffffff)
Rebooting in 86400 seconds..


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Aug 3, 2019, 4:11:03 AM8/3/19
to syzkaller-a...@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