All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+a88c8270030dc5d71e4f@syzkaller.appspotmail.com>
To: aivazian.tigran@gmail.com, akpm@linux-foundation.org,
	dmitri.vorobiev@gmail.com, gregkh@linuxfoundation.org,
	kstewart@linuxfoundation.org, linux-kernel@vger.kernel.org,
	pombredanne@nexb.com, snakebyte@gmx.de,
	syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
	tigran@aivazian.fsnet.co.uk, torvalds@linux-foundation.org,
	viro@zeniv.linux.org.uk
Subject: Re: KASAN: slab-out-of-bounds Read in find_first_zero_bit
Date: Thu, 07 Nov 2019 05:42:04 -0800	[thread overview]
Message-ID: <000000000000b207e60596c1d413@google.com> (raw)
In-Reply-To: <001a113ed49eb535d20568bb75ba@google.com>

syzbot suspects this bug was fixed by commit:

commit d1877155891020cb26ad4fba45bfee52d8da9951
Author: Tigran Aivazian <aivazian.tigran@gmail.com>
Date:   Thu Jan 3 23:28:14 2019 +0000

     bfs: extra sanity checking and static inode bitmap

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=16634ee8600000
start commit:   b5dbc287 Merge tag 'kbuild-fixes-v4.16-3' of git://git.ker..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=d9b0d91297e224bc
dashboard link: https://syzkaller.appspot.com/bug?extid=a88c8270030dc5d71e4f
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=16cf65d3800000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16d99ab3800000

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

#syz fix: bfs: extra sanity checking and static inode bitmap

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

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-31 20:47 KASAN: slab-out-of-bounds Read in find_first_zero_bit syzbot
2019-11-07 13:42 ` syzbot [this message]
2019-11-07 19:14   ` Tigran Aivazian
2018-03-31 20:47 syzbot

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=000000000000b207e60596c1d413@google.com \
    --to=syzbot+a88c8270030dc5d71e4f@syzkaller.appspotmail.com \
    --cc=aivazian.tigran@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dmitri.vorobiev@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pombredanne@nexb.com \
    --cc=snakebyte@gmx.de \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=tigran@aivazian.fsnet.co.uk \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.