linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+cd4b9b3648c78dbd7fca@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	miklos@szeredi.hu, mszeredi@redhat.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: slab-out-of-bounds Write in end_requests
Date: Thu, 07 Nov 2019 05:42:05 -0800	[thread overview]
Message-ID: <000000000000b6a0aa0596c1d4df@google.com> (raw)
In-Reply-To: <000000000000d0429205723824d8@google.com>

syzbot suspects this bug was fixed by commit:

commit 45ff350bbd9d0f0977ff270a0d427c71520c0c37
Author: Miklos Szeredi <mszeredi@redhat.com>
Date:   Thu Jul 26 14:13:11 2018 +0000

     fuse: fix unlocked access to processing queue

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1494e3ec600000
start commit:   dd63bf22 Merge branch 'i2c/for-current' of git://git.kerne..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=ffb4428fdc82f93b
dashboard link: https://syzkaller.appspot.com/bug?extid=cd4b9b3648c78dbd7fca
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11b9732c400000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16c469a4400000

If the result looks correct, please mark the bug fixed by replying with:

#syz fix: fuse: fix unlocked access to processing queue

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      reply	other threads:[~2019-11-07 13:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30 14:19 KASAN: slab-out-of-bounds Write in end_requests syzbot
2019-11-07 13:42 ` syzbot [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=000000000000b6a0aa0596c1d4df@google.com \
    --to=syzbot+cd4b9b3648c78dbd7fca@syzkaller.appspotmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mszeredi@redhat.com \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).