All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+60bfed6b415fbd1fbb87@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in __lock_sock
Date: Fri, 24 Nov 2023 04:22:06 -0800	[thread overview]
Message-ID: <000000000000243722060ae50083@google.com> (raw)
In-Reply-To: <tencent_38DDEF5DB0192CCFD60D8BA5AA8DA1924107@qq.com>

Hello,

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

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

Tested on:

commit:         8de1e7af Merge branch 'for-next/core' into for-kernelci
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=17a2cff0e80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=3e6feaeda5dcbc27
dashboard link: https://syzkaller.appspot.com/bug?extid=60bfed6b415fbd1fbb87
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
patch:          https://syzkaller.appspot.com/x/patch.diff?x=15b4f40ce80000

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

       reply	other threads:[~2023-11-24 12:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_38DDEF5DB0192CCFD60D8BA5AA8DA1924107@qq.com>
2023-11-24 12:22 ` syzbot [this message]
     [not found] <tencent_148DEA923ADD925D92193DCF888DACA5B807@qq.com>
2023-11-25  3:47 ` [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in __lock_sock syzbot
     [not found] <tencent_10DE52D4065BC98B6EC92ECCCCB3E7C34606@qq.com>
2023-11-25  1:58 ` syzbot
     [not found] <tencent_8E3BCF900DCF25FA0DA212145DC45DDF1907@qq.com>
2023-11-24 14:36 ` syzbot
     [not found] <tencent_ABBB2A33F49E801B384B7B1BC02538BA4A08@qq.com>
2023-11-24 11:56 ` syzbot
     [not found] <tencent_93DC466109A02ECE6EC20CAE67D5C6CCD206@qq.com>
2023-11-23 14:27 ` syzbot
     [not found] <tencent_D3FF464CC98C2ED92ED18C9367E746E65206@qq.com>
2023-11-23  3:06 ` syzbot
     [not found] <tencent_370274657663662E3C37373E97B236864A09@qq.com>
2023-11-23  1:35 ` syzbot
2023-11-23  2:06   ` syzbot
2023-11-23  3:19   ` syzbot
2023-11-24 11:29   ` syzbot
2023-11-24 11:41   ` syzbot
2023-11-24 13:54   ` syzbot
2023-11-25  1:31   ` syzbot
2023-11-25  3:20   ` syzbot
2023-11-23  1:14 syzbot
  -- strict thread matches above, loose matches on Subject: below --
2023-11-22 15:43 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=000000000000243722060ae50083@google.com \
    --to=syzbot+60bfed6b415fbd1fbb87@syzkaller.appspotmail.com \
    --cc=eadavis@qq.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.