All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+dec4d528fb7a7c5d8ce3@syzkaller.appspotmail.com>
To: davem@davemloft.net, eadavis@sina.com, edumazet@google.com,
	 hdanton@sina.com, johan.hedberg@gmail.com, kuba@kernel.org,
	 linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	 luiz.dentz@gmail.com, luiz.von.dentz@intel.com,
	marcel@holtmann.org,  netdev@vger.kernel.org, pabeni@redhat.com,
	pav@iki.fi,  syzkaller-bugs@googlegroups.com,
	william.xuanziyang@huawei.com
Subject: Re: [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in __sco_sock_close
Date: Sun, 26 Nov 2023 23:13:04 -0800	[thread overview]
Message-ID: <0000000000007fd73e060b1d08ec@google.com> (raw)
In-Reply-To: <0000000000007f826b06044878ed@google.com>

syzbot suspects this issue was fixed by commit:

commit 181a42edddf51d5d9697ecdf365d72ebeab5afb0
Author: Ziyang Xuan <william.xuanziyang@huawei.com>
Date:   Wed Oct 11 09:57:31 2023 +0000

    Bluetooth: Make handle of hci_conn be unique

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=140ffa0ce80000
start commit:   bd6c11bc43c4 Merge tag 'net-next-6.6' of git://git.kernel...
git tree:       net-next
kernel config:  https://syzkaller.appspot.com/x/.config?x=634e05b4025da9da
dashboard link: https://syzkaller.appspot.com/bug?extid=dec4d528fb7a7c5d8ce3
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=145586a8680000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13bf8dffa80000

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

#syz fix: Bluetooth: Make handle of hci_conn be unique

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

      parent reply	other threads:[~2023-11-27  7:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01  9:06 [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in __sco_sock_close syzbot
2023-09-01 21:09 ` syzbot
2023-09-10 22:43 ` syzbot
2023-11-27  7:13 ` 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=0000000000007fd73e060b1d08ec@google.com \
    --to=syzbot+dec4d528fb7a7c5d8ce3@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=eadavis@sina.com \
    --cc=edumazet@google.com \
    --cc=hdanton@sina.com \
    --cc=johan.hedberg@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=luiz.von.dentz@intel.com \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pav@iki.fi \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=william.xuanziyang@huawei.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 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.