general protection fault in bdev_read_page

[syzbot]

Hello,

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


CC: [vi...@zeniv.linux.org.uk linux-...@vger.kernel.org
linux-...@vger.kernel.org]

kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 1 PID: 11411 Comm: syz-executor1 Not tainted 4.13.0-rc3+ #12
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
task: ffff8801cf8481c0 task.stack: ffff8801c5e48000
RIP: 0010:bdev_read_page+0x38/0x210 fs/block_dev.c:671
RSP: 0018:ffff8801c5e4e8a8 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffc90001f23000
RDX: 000000000000001c RSI: ffffffff81b28810 RDI: 00000000000000e0
RBP: ffff8801c5e4e8d8 R08: ffff8801c5e4edc0 R09: ffff8801c5e4ecc0
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 000000000000a080 R14: ffffea00063b58e0 R15: 0000000000000000
FS: 00007fc8e067e700(0000) GS:ffff8801dc100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020ae6000 CR3: 00000001d1949000 CR4: 00000000001406e0
DR0: 0000000020000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
do_mpage_readpage+0x1507/0x19e0 fs/mpage.c:281
mpage_readpages+0x626/0x8a0 fs/mpage.c:382
blkdev_readpages+0x2c/0x40 fs/block_dev.c:589
read_pages mm/readahead.c:121 [inline]
__do_page_cache_readahead+0x6c6/0xc00 mm/readahead.c:199
ra_submit mm/internal.h:66 [inline]
ondemand_readahead+0x514/0xa70 mm/readahead.c:478
page_cache_sync_readahead+0xaa/0x100 mm/readahead.c:510
do_generic_file_read mm/filemap.c:1939 [inline]
generic_file_read_iter+0x163b/0x26b0 mm/filemap.c:2202
blkdev_read_iter+0x105/0x170 fs/block_dev.c:1917
call_read_iter include/linux/fs.h:1737 [inline]
generic_file_splice_read+0x3f9/0x7b0 fs/splice.c:307
do_splice_to+0x10a/0x160 fs/splice.c:896
splice_direct_to_actor+0x242/0x820 fs/splice.c:968
do_splice_direct+0x29b/0x3c0 fs/splice.c:1077
do_sendfile+0x5c9/0xe80 fs/read_write.c:1412
SYSC_sendfile64 fs/read_write.c:1467 [inline]
SyS_sendfile64+0xbd/0x160 fs/read_write.c:1459
entry_SYSCALL_64_fastpath+0x1f/0xbe
RIP: 0033:0x4512c9
RSP: 002b:00007fc8e067dc08 EFLAGS: 00000216 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 0000000000718000 RCX: 00000000004512c9
RDX: 00000000202c6000 RSI: 0000000000000017 RDI: 0000000000000017
RBP: 0000000000000082 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000004 R11: 0000000000000216 R12: 00000000004b9621
R13: 00000000ffffffff R14: 0000000020ced000 R15: 0000000000000880
Code: 89 f5 53 48 89 fb 48 83 ec 08 48 89 55 d0 e8 e0 e8 ba ff 48 8d bb e0
00 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00
0f 85 78 01 00 00 4c 8b a3 e0 00 00 00 48 b8 00 00
RIP: bdev_read_page+0x38/0x210 fs/block_dev.c:671 RSP: ffff8801c5e4e8a8
---[ end trace 211f65ef336a7124 ]---
unregister_netdevice: waiting for syz4 to become free. Usage count = 1
dccp_v6_rcv: dropped packet with invalid checksum
dccp_v6_rcv: dropped packet with invalid checksum
dccp_v6_rcv: dropped packet with invalid checksum
dccp_v6_rcv: dropped packet with invalid checksum


---
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.
To upstream this report, please reply with:
#syz upstream

[Dmitry Vyukov]

Stopped happening in August, no repro

#syz invalid

On Tue, Oct 31, 2017 at 2:57 PM, syzbot
<bot+ad92c93c0ac840556e...@syzkaller.appspotmail.com>
wrote:

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