From: syzbot <syzbot+47de774a425e2380f16f@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] WARNING in wnd_init (2)
Date: Mon, 07 Oct 2024 20:37:03 -0700 [thread overview]
Message-ID: <6704a8df.050a0220.49194.0521.GAE@google.com> (raw)
In-Reply-To: <66f70232.050a0220.38ace9.002f.GAE@google.com>
syzbot has bisected this issue to:
commit fc471e39e38fea6677017cbdd6d928088a59fc67
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Fri Jun 30 12:12:58 2023 +0000
fs/ntfs3: Use kvmalloc instead of kmalloc(... __GFP_NOWARN)
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10a4bb80580000
start commit: 8cf0b93919e1 Linux 6.12-rc2
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=12a4bb80580000
console output: https://syzkaller.appspot.com/x/log.txt?x=14a4bb80580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7a3fccdd0bb995
dashboard link: https://syzkaller.appspot.com/bug?extid=47de774a425e2380f16f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17ab2707980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10dbc327980000
Reported-by: syzbot+47de774a425e2380f16f@syzkaller.appspotmail.com
Fixes: fc471e39e38f ("fs/ntfs3: Use kvmalloc instead of kmalloc(... __GFP_NOWARN)")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-10-08 3:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 19:06 [syzbot] [ntfs3?] WARNING in wnd_init (2) syzbot
2024-10-08 3:37 ` syzbot [this message]
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=6704a8df.050a0220.49194.0521.GAE@google.com \
--to=syzbot+47de774a425e2380f16f@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox