From: syzbot <syzbot+7e46cdef14bf496a3ab4@syzkaller.appspotmail.com>
To: 42.hyeyoo@gmail.com, akpm@linux-foundation.org,
andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
cl@linux.com, daniel@iogearbox.net, eddyz87@gmail.com,
feng.tang@intel.com, haoluo@google.com, iamjoonsoo.kim@lge.com,
john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
martin.lau@linux.dev, penberg@kernel.org, rientjes@google.com,
roman.gushchin@linux.dev, sdf@fomichev.me, song@kernel.org,
syzkaller-bugs@googlegroups.com, vbabka@suse.cz,
yonghong.song@linux.dev
Subject: Re: [syzbot] [bpf?] WARNING in push_jmp_history
Date: Tue, 08 Oct 2024 01:43:03 -0700 [thread overview]
Message-ID: <6704f097.050a0220.1e4d62.0087.GAE@google.com> (raw)
In-Reply-To: <670429f6.050a0220.49194.0517.GAE@google.com>
syzbot has bisected this issue to:
commit d0a38fad51cc70ab3dd3c59b54d8079ac19220b9
Author: Feng Tang <feng.tang@intel.com>
Date: Wed Sep 11 06:45:34 2024 +0000
mm/slub: Improve redzone check and zeroing for krealloc()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11ddbb80580000
start commit: c02d24a5af66 Add linux-next specific files for 20241003
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=13ddbb80580000
console output: https://syzkaller.appspot.com/x/log.txt?x=15ddbb80580000
kernel config: https://syzkaller.appspot.com/x/.config?x=94f9caf16c0af42d
dashboard link: https://syzkaller.appspot.com/bug?extid=7e46cdef14bf496a3ab4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10b82707980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16f4c327980000
Reported-by: syzbot+7e46cdef14bf496a3ab4@syzkaller.appspotmail.com
Fixes: d0a38fad51cc ("mm/slub: Improve redzone check and zeroing for krealloc()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2024-10-08 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <670429f6.050a0220.49194.0517.GAE@google.com>
2024-10-08 8:43 ` syzbot [this message]
2024-10-08 9:41 ` Eduard Zingerman
2024-10-08 10:01 ` Vlastimil Babka
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=6704f097.050a0220.1e4d62.0087.GAE@google.com \
--to=syzbot+7e46cdef14bf496a3ab4@syzkaller.appspotmail.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cl@linux.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=feng.tang@intel.com \
--cc=haoluo@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=martin.lau@linux.dev \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@suse.cz \
--cc=yonghong.song@linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox