From: syzbot <syzbot+4376a9a073770c173269@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, clm@fb.com, dsterba@suse.com,
dsterba@suse.cz, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com,
torvalds@linux-foundation.org, w@1wt.eu
Subject: Re: [syzbot] [btrfs?] WARNING: kmalloc bug in btrfs_ioctl_send
Date: Sun, 22 Jan 2023 03:14:21 -0800 [thread overview]
Message-ID: <0000000000006e58cb05f2d86236@google.com> (raw)
In-Reply-To: <00000000000075a52e05ee97ad74@google.com>
syzbot has bisected this issue to:
commit 7661809d493b426e979f39ab512e3adf41fbcc69
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Wed Jul 14 16:45:49 2021 +0000
mm: don't allow oversized kvmalloc() calls
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13f2c851480000
start commit: f9ff5644bcc0 Merge tag 'hsi-for-6.2' of git://git.kernel.o..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=100ac851480000
console output: https://syzkaller.appspot.com/x/log.txt?x=17f2c851480000
kernel config: https://syzkaller.appspot.com/x/.config?x=827916bd156c2ec6
dashboard link: https://syzkaller.appspot.com/bug?extid=4376a9a073770c173269
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1775aed7880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11cbcbd0480000
Reported-by: syzbot+4376a9a073770c173269@syzkaller.appspotmail.com
Fixes: 7661809d493b ("mm: don't allow oversized kvmalloc() calls")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-01-22 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 8:21 [syzbot] WARNING: kmalloc bug in btrfs_ioctl_send syzbot
2022-11-29 15:56 ` David Sterba
2022-12-02 15:15 ` Wang Yugui
2022-12-05 17:26 ` David Sterba
2023-01-22 11:14 ` syzbot [this message]
2023-01-22 19:53 ` [syzbot] [btrfs?] " Linus Torvalds
2023-01-24 17:47 ` David Sterba
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=0000000000006e58cb05f2d86236@google.com \
--to=syzbot+4376a9a073770c173269@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/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