From: syzbot <syzbot+683f8cb11b94b1824c77@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 Read in skb_queue_purge_reason (2)
Date: Wed, 05 Feb 2025 03:31:05 -0800 [thread overview]
Message-ID: <67a34bf9.050a0220.50516.003f.GAE@google.com> (raw)
In-Reply-To: <20250205110528.1938-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+683f8cb11b94b1824c77@syzkaller.appspotmail.com
Tested-by: syzbot+683f8cb11b94b1824c77@syzkaller.appspotmail.com
Tested on:
commit: ed88b8b8 Add linux-next specific files for 20250205
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=150a3eb0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2d80d4f62382148d
dashboard link: https://syzkaller.appspot.com/bug?extid=683f8cb11b94b1824c77
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1680e318580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-02-05 11:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 8:44 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in skb_queue_purge_reason (2) syzbot
2025-02-04 14:48 ` syzbot
2025-02-05 11:05 ` Hillf Danton
2025-02-05 11:31 ` syzbot [this message]
2025-02-10 11:26 ` syzbot
2025-02-11 14:16 ` [DMARC error] " Arseniy Krasnov
2025-02-11 16:22 ` Arseniy Krasnov
2025-02-11 16:51 ` Luiz Augusto von Dentz
2025-02-12 6:05 ` Arseniy Krasnov
2025-02-12 6:49 ` [syzbot] " syzbot
[not found] <0cc53c2e-a7cc-74ea-a5f0-928af997ecf7@salutedevices.com>
2025-02-12 7:14 ` 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=67a34bf9.050a0220.50516.003f.GAE@google.com \
--to=syzbot+683f8cb11b94b1824c77@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.