WARNING in __mark_inode_dirty

[syzbot]

Hello,

syzkaller hit the following crash on
1deab8ce2c91e3b16563b7a7ea150f82334262ec
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-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.


kvm [6775]: vcpu0, guest rIP: 0x9112 Hyper-V uhandled wrmsr: 0x4000008f
data 0x4141
------------[ cut here ]------------
bdi-block not registered
WARNING: CPU: 0 PID: 6791 at fs/fs-writeback.c:2194
__mark_inode_dirty+0x67a/0x1170 fs/fs-writeback.c:2192
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 6791 Comm: syz-executor3 Not tainted 4.14.0+ #183
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
panic+0x1e4/0x41c kernel/panic.c:183
__warn+0x1dc/0x200 kernel/panic.c:547
report_bug+0x211/0x2d0 lib/bug.c:184
fixup_bug.part.11+0x37/0x80 arch/x86/kernel/traps.c:177
fixup_bug arch/x86/kernel/traps.c:246 [inline]
do_error_trap+0x2d7/0x3e0 arch/x86/kernel/traps.c:295
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:314
invalid_op+0x18/0x20 arch/x86/entry/entry_64.S:926
RIP: 0010:__mark_inode_dirty+0x67a/0x1170 fs/fs-writeback.c:2192
RSP: 0018:ffff8801d782ef10 EFLAGS: 00010286
RAX: dffffc0000000008 RBX: ffff8801dac051f8 RCX: ffffffff815992ae
RDX: 0000000000000c09 RSI: ffffc90002a73000 RDI: 0000000000000212
RBP: ffff8801d782f178 R08: 1ffff1003af05d75 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8801c8a02458
R13: ffff8801c8a02400 R14: ffff8801dac052d8 R15: 0000000000000000
mark_buffer_dirty+0x484/0x5d0 fs/buffer.c:1136
__block_commit_write.isra.32+0x13b/0x2f0 fs/buffer.c:2060
block_write_end+0x99/0x1c0 fs/buffer.c:2138
blkdev_write_end+0xc3/0x280 fs/block_dev.c:593
generic_perform_write+0x3a4/0x600 mm/filemap.c:3150
__generic_file_write_iter+0x366/0x5b0 mm/filemap.c:3264
blkdev_write_iter+0x207/0x3e0 fs/block_dev.c:1893
call_write_iter include/linux/fs.h:1772 [inline]
do_iter_readv_writev+0x531/0x7f0 fs/read_write.c:653
do_iter_write+0x15a/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+0x2a7/0x3d0 fs/splice.c:1061
do_sendfile+0x5d5/0xe90 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:0x452879
RSP: 002b:00007f1b5916fbe8 EFLAGS: 00000212 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 0000000000758020 RCX: 0000000000452879
RDX: 0000000020528ff8 RSI: 0000000000000014 RDI: 0000000000000014
RBP: 0000000000000086 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000080000001 R11: 0000000000000212 R12: 00000000006f3070
R13: 00000000ffffffff R14: 00007f1b591706d4 R15: 0000000000000000
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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 committed, please 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.

[Dmitry Vyukov]

old bug bankruptcy

#syz invalid

On Wed, Nov 22, 2017 at 9:39 AM, syzbot
<bot+ecd1588da6c1c32b56...@syzkaller.appspotmail.com>
wrote:

> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-bug...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-bugs/001a113ece8c81a2c3055e8e423e%40google.com.
> For more options, visit https://groups.google.com/d/optout.