From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io0-f200.google.com ([209.85.223.200]:50030 "EHLO mail-io0-f200.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731165AbeG3PyS (ORCPT ); Mon, 30 Jul 2018 11:54:18 -0400 Received: by mail-io0-f200.google.com with SMTP id k9-v6so8921437iob.16 for ; Mon, 30 Jul 2018 07:19:05 -0700 (PDT) MIME-Version: 1.0 Date: Mon, 30 Jul 2018 07:19:04 -0700 Message-ID: <000000000000d0429205723824d8@google.com> Subject: KASAN: slab-out-of-bounds Write in end_requests From: syzbot To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, miklos@szeredi.hu, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8"; format=flowed; delsp=yes Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hello, syzbot found the following crash on: HEAD commit: dd63bf22fccd Merge branch 'i2c/for-current' of git://git.k.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10b9c770400000 kernel config: https://syzkaller.appspot.com/x/.config?x=ffb4428fdc82f93b dashboard link: https://syzkaller.appspot.com/bug?extid=cd4b9b3648c78dbd7fca compiler: gcc (GCC) 8.0.1 20180413 (experimental) syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=11b9732c400000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16c469a4400000 IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+cd4b9b3648c78dbd7fca@syzkaller.appspotmail.com ================================================================== BUG: KASAN: slab-out-of-bounds in end_requests+0x37b/0x460 fs/fuse/dev.c:2042 Write of size 4 at addr ffff8801c71b2fe4 by task syz-executor467/7211 CPU: 0 PID: 7211 Comm: syz-executor467 Not tainted 4.18.0-rc6+ #166 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113 ? dump_stack_print_info.cold.2 --- 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 syzkaller@googlegroups.com. syzbot will keep track of this bug report. See: https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with syzbot. syzbot can test patches for this bug, for details see: https://goo.gl/tpsmEJ#testing-patches