linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+b364ed862aa07c74bc62@syzkaller.appspotmail.com>
To: bigeasy@linutronix.de, davem@davemloft.net, dvyukov@google.com,
	jack@suse.cz, johan.hedberg@gmail.com,
	linux-bluetooth@vger.kernel.org, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org, marcel@holtmann.org,
	mmarek@suse.com, netdev@vger.kernel.org,
	syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
	torvalds@linux-foundation.org, xiyou.wangcong@gmail.com
Subject: Re: KASAN: use-after-free Write in hci_sock_release
Date: Sat, 16 May 2020 14:27:03 -0700	[thread overview]
Message-ID: <00000000000044329005a5ca97eb@google.com> (raw)
In-Reply-To: <0000000000003692760578e651dd@google.com>

syzbot suspects this bug was fixed by commit:

commit f1e67e355c2aafeddf1eac31335709236996d2fe
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Mon Nov 18 13:28:24 2019 +0000

    fs/buffer: Make BH_Uptodate_Lock bit_spin_lock a regular spinlock_t

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1761ce06100000
start commit:   645ff1e8 Merge branch 'for-linus' of git://git.kernel.org/..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=7308e68273924137
dashboard link: https://syzkaller.appspot.com/bug?extid=b364ed862aa07c74bc62
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=152532bb400000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13f73320c00000

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

#syz fix: fs/buffer: Make BH_Uptodate_Lock bit_spin_lock a regular spinlock_t

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

      parent reply	other threads:[~2020-05-16 21:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23 14:38 KASAN: use-after-free Write in hci_sock_release syzbot
2019-01-04  9:27 ` syzbot
2019-03-22 12:04 ` syzbot
2019-03-22 12:16   ` Dmitry Vyukov
2019-03-23 20:25     ` Cong Wang
2019-03-25  8:04       ` Dmitry Vyukov
2020-05-16 21:27 ` 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=00000000000044329005a5ca97eb@google.com \
    --to=syzbot+b364ed862aa07c74bc62@syzkaller.appspotmail.com \
    --cc=bigeasy@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=dvyukov@google.com \
    --cc=jack@suse.cz \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mmarek@suse.com \
    --cc=netdev@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=xiyou.wangcong@gmail.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).