WARNING in __mark_inode_dirty (2)

11 views
Skip to first unread message

syzbot

unread,
Jul 21, 2020, 12:03:21 PM7/21/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: b850307b Linux 4.14.184
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16e31230900000
kernel config: https://syzkaller.appspot.com/x/.config?x=ddc0f08dd6b981c5
dashboard link: https://syzkaller.appspot.com/bug?extid=2bbc8c337258efea6df9
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

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

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

bdi-block not registered
------------[ cut here ]------------
WARNING: CPU: 0 PID: 25999 at fs/fs-writeback.c:2207 __mark_inode_dirty.cold+0x31/0x42 fs/fs-writeback.c:2207
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 25999 Comm: syz-executor.3 Not tainted 4.14.184-syzkaller #0
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+0x1b2/0x283 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x2f/0x30 kernel/panic.c:547
report_bug+0x20a/0x248 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:964
RIP: 0010:__mark_inode_dirty.cold+0x31/0x42 fs/fs-writeback.c:2207
RSP: 0018:ffff88805c617538 EFLAGS: 00010286
RAX: 0000000000000018 RBX: ffff8880325ad818 RCX: 0000000000000000
RDX: 000000000000a626 RSI: ffffffff81499420 RDI: ffffed100b8c2e9d
RBP: ffff888064d86218 R08: 0000000000000018 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888064d861c0
R13: ffff8880325ad8f0 R14: ffff8880325ad8a0 R15: 0000000000000000
mark_buffer_dirty+0x337/0x480 fs/buffer.c:1177
__block_commit_write.isra.0+0x138/0x210 fs/buffer.c:2111
block_write_end+0x42/0xf0 fs/buffer.c:2189
blkdev_write_end+0x3c/0x1f0 fs/block_dev.c:620
generic_perform_write+0x268/0x420 mm/filemap.c:3058
__generic_file_write_iter+0x227/0x590 mm/filemap.c:3172
blkdev_write_iter fs/block_dev.c:1914 [inline]
blkdev_write_iter+0x1e8/0x3a0 fs/block_dev.c:1891
call_write_iter include/linux/fs.h:1778 [inline]
do_iter_readv_writev+0x3df/0x600 fs/read_write.c:675
do_iter_write fs/read_write.c:954 [inline]
do_iter_write+0x152/0x550 fs/read_write.c:935
vfs_iter_write+0x70/0xa0 fs/read_write.c:967
iter_file_splice_write+0x52e/0xa10 fs/splice.c:749
do_splice_from fs/splice.c:851 [inline]
direct_splice_actor+0x115/0x160 fs/splice.c:1018
splice_direct_to_actor+0x27e/0x730 fs/splice.c:973
do_splice_direct+0x164/0x210 fs/splice.c:1061
do_sendfile+0x469/0xaf0 fs/read_write.c:1441
SYSC_sendfile64 fs/read_write.c:1502 [inline]
SyS_sendfile64+0xff/0x110 fs/read_write.c:1488
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45c1f9
RSP: 002b:00007f3b85db6c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00000000000260c0 RCX: 000000000045c1f9
RDX: 0000000000000000 RSI: 0000000000000007 RDI: 0000000000000006
RBP: 000000000078c128 R08: 0000000000000000 R09: 0000000000000000
R10: 0020000102000003 R11: 0000000000000246 R12: 000000000078c0ec
R13: 00007ffcfa3dad2f R14: 00007f3b85db79c0 R15: 000000000078c0ec
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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,
Jul 3, 2021, 11:16:11 AM7/3/21
to syzkaller...@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