From: syzbot <syzbot+6c1861115b4253e45969@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] KASAN: slab-use-after-free Read in futex_unqueue
Date: Tue, 10 Feb 2026 22:55:04 -0800 [thread overview]
Message-ID: <698c27c8.050a0220.2eeac1.0095.GAE@google.com> (raw)
In-Reply-To: <20260211063113.2881-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+6c1861115b4253e45969@syzkaller.appspotmail.com
Tested-by: syzbot+6c1861115b4253e45969@syzkaller.appspotmail.com
Tested on:
commit: 192c0159 Merge tag 'powerpc-7.0-1' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17e56ae6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=aaa1d655bee4457b
dashboard link: https://syzkaller.appspot.com/bug?extid=6c1861115b4253e45969
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch: https://syzkaller.appspot.com/x/patch.diff?x=15048e5a580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-02-11 6:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 21:43 [syzbot] [kernel?] KASAN: slab-use-after-free Read in futex_unqueue syzbot
2026-02-10 22:51 ` Hillf Danton
2026-02-10 23:15 ` syzbot
2026-02-11 0:38 ` Hillf Danton
2026-02-11 0:55 ` syzbot
2026-02-11 3:31 ` Forwarded: [PATCH] futex: Fix use-after-free in futex_unqueue() on private hash teardown syzbot
2026-02-11 8:14 ` Thomas Gleixner
2026-02-11 6:31 ` [syzbot] [kernel?] KASAN: slab-use-after-free Read in futex_unqueue Hillf Danton
2026-02-11 6:55 ` syzbot [this message]
2026-02-11 9:22 ` Hillf Danton
2026-02-11 9:46 ` syzbot
[not found] <20260211033121.713551-1-suunj1331@gmail.com>
2026-02-11 3:49 ` 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=698c27c8.050a0220.2eeac1.0095.GAE@google.com \
--to=syzbot+6c1861115b4253e45969@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.