WARNING in __set_page_dirty

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 4ba3f691 UPSTREAM: xfrm: fix ptr_ret.cocci warnings
git tree: android-4.9
console output: https://syzkaller.appspot.com/x/log.txt?x=14172447400000
kernel config: https://syzkaller.appspot.com/x/.config?x=13558268b29d9d4a
dashboard link: https://syzkaller.appspot.com/bug?extid=1c1422f1da95f673b06d
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+1c1422...@syzkaller.appspotmail.com

EXT4-fs (sda1): free_blocks=12631
EXT4-fs (sda1): dirty_blocks=438
EXT4-fs (sda1): Block reservation details
EXT4-fs (sda1): i_reserved_data_blocks=168
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5655 at fs/buffer.c:634 __set_page_dirty+0x188/0x1f0
fs/buffer.c:634
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 5655 Comm: syz-executor2 Not tainted 4.9.135+ #113
ffff8801d3a37200 ffffffff81b36bf9 ffffffff82a38ba0 00000000ffffffff
0000000000000000 0000000000000001 000000000000027a ffff8801d3a372c0
ffffffff813f6aa5 0000000041b58ab3 ffffffff82e2a6e3 ffffffff813f68e6
Call Trace:
[<ffffffff81b36bf9>] __dump_stack lib/dump_stack.c:15 [inline]
[<ffffffff81b36bf9>] dump_stack+0xc1/0x128 lib/dump_stack.c:51
[<ffffffff813f6aa5>] panic+0x1bf/0x39f kernel/panic.c:179
[<ffffffff813f6d74>] __warn.cold.9+0xc1/0x17f kernel/panic.c:542
[<ffffffff810dbe2c>] warn_slowpath_null+0x2c/0x40 kernel/panic.c:585
[<ffffffff815b8148>] __set_page_dirty+0x188/0x1f0 fs/buffer.c:634
[<ffffffff815b8309>] __set_page_dirty_buffers+0x159/0x230 fs/buffer.c:694
[<ffffffff8142c982>] set_page_dirty+0x162/0x2d0 mm/page-writeback.c:2554
[<ffffffff8142cb57>] set_page_dirty_lock+0x67/0xa0 mm/page-writeback.c:2579
[<ffffffff815ccfca>] dio_bio_complete+0x40a/0x4e0 fs/direct-io.c:495
[<ffffffff815d6847>] dio_await_completion fs/direct-io.c:517 [inline]
[<ffffffff815d6847>] do_blockdev_direct_IO fs/direct-io.c:1331 [inline]
[<ffffffff815d6847>] __blockdev_direct_IO+0x8c27/0xbd10 fs/direct-io.c:1360
[<ffffffff816de598>] ext4_direct_IO_read fs/ext4/inode.c:3604 [inline]
[<ffffffff816de598>] ext4_direct_IO+0xc68/0x29c0 fs/ext4/inode.c:3661
[<ffffffff8141373b>] generic_file_read_iter+0x83b/0x1a80 mm/filemap.c:1964
[<ffffffff81507628>] do_iter_readv_writev+0x2f8/0x4b0 fs/read_write.c:693
[<ffffffff8150b21a>] do_readv_writev+0x2fa/0x7b0 fs/read_write.c:871
[<ffffffff8150b754>] vfs_readv+0x84/0xc0 fs/read_write.c:897
[<ffffffff8150bb87>] do_preadv+0x197/0x240 fs/read_write.c:974
[<ffffffff8150f140>] SYSC_preadv fs/read_write.c:1024 [inline]
[<ffffffff8150f140>] SyS_preadv+0x30/0x40 fs/read_write.c:1019
[<ffffffff810056ef>] do_syscall_64+0x19f/0x550 arch/x86/entry/common.c:285
[<ffffffff8280ac13>] entry_SYSCALL_64_after_swapgs+0x5d/0xdb
Kernel Offset: disabled
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]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.