From: syzbot <syzbot+59701a78e84b0bccfe1b@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [trace?] [bpf?] KASAN: slab-use-after-free Read in bpf_trace_run2 (3)
Date: Sat, 21 Feb 2026 15:51:01 -0800 [thread overview]
Message-ID: <699a44e5.050a0220.340abe.0d2d.GAE@google.com> (raw)
In-Reply-To: <20260221233436.24624-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
lost connection to test machine
Tested on:
commit: fa5c82f4 slab.h: disable completely broken overflow ha..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17570006580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2208a171312e89b7
dashboard link: https://syzkaller.appspot.com/bug?extid=59701a78e84b0bccfe1b
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=11a3f95a580000
next parent reply other threads:[~2026-02-21 23:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260221233436.24624-1-kartikey406@gmail.com>
2026-02-21 23:51 ` syzbot [this message]
[not found] <20260221120701.23186-1-kartikey406@gmail.com>
2026-02-21 12:24 ` [syzbot] [trace?] [bpf?] KASAN: slab-use-after-free Read in bpf_trace_run2 (3) syzbot
[not found] <20260221104518.20576-1-kartikey406@gmail.com>
2026-02-21 11:02 ` syzbot
[not found] <20260221064152.17909-1-kartikey406@gmail.com>
2026-02-21 6:58 ` syzbot
[not found] <20260221054116.15285-1-kartikey406@gmail.com>
2026-02-21 5:58 ` syzbot
[not found] <20260221051921.14826-1-kartikey406@gmail.com>
2026-02-21 5:37 ` syzbot
2026-02-21 4:46 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=699a44e5.050a0220.340abe.0d2d.GAE@google.com \
--to=syzbot+59701a78e84b0bccfe1b@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.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.