All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+cf54c1da6574b6c1b049@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in sco_chan_del
Date: Fri, 18 Aug 2023 19:10:32 -0700	[thread overview]
Message-ID: <0000000000006dbd3606033d26fa@google.com> (raw)
In-Reply-To: <20230819014631.2196-1-hdanton@sina.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+cf54c1da6574b6c1b049@syzkaller.appspotmail.com

Tested on:

commit:         47762f08 Add linux-next specific files for 20230817
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1738036fa80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=ed03cf326b3ef94c
dashboard link: https://syzkaller.appspot.com/bug?extid=cf54c1da6574b6c1b049
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1400439ba80000

Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2023-08-19  2:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230819014631.2196-1-hdanton@sina.com>
2023-08-19  2:10 ` syzbot [this message]
2023-08-19 13:33 [PATCH] Bluetooth: hci_conn: fail SCO/ISO via hci_conn_failed if ACL gone early Pauli Virtanen
2023-08-19 14:01 ` [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in sco_chan_del syzbot
     [not found] <20230818114835.2133-1-hdanton@sina.com>
2023-08-18 14:05 ` syzbot
  -- strict thread matches above, loose matches on Subject: below --
2023-05-15 12:47 syzbot
2023-05-15 16:01 ` Ruihan Li
2023-08-17 12:56 ` syzbot
2023-08-18  4:39 ` 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=0000000000006dbd3606033d26fa@google.com \
    --to=syzbot+cf54c1da6574b6c1b049@syzkaller.appspotmail.com \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.