From: syzbot <syzbot+6783b9aaa6a224fabde8@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] INFO: trying to register non-static key in do_mpage_readpage (2)
Date: Fri, 30 Aug 2024 03:44:02 -0700 [thread overview]
Message-ID: <00000000000001a0600620e4451b@google.com> (raw)
In-Reply-To: <0000000000008886db06150bcc92@google.com>
syzbot has bisected this issue to:
commit 24c5100aceedcd47af89aaa404d4c96cd2837523
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Tue Jun 4 07:41:39 2024 +0000
fs/ntfs3: Fix getting file type
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1104eb2f980000
start commit: d5d547aa7b51 Merge tag 'random-6.11-rc6-for-linus' of git:..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1304eb2f980000
console output: https://syzkaller.appspot.com/x/log.txt?x=1504eb2f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=d806687521800cad
dashboard link: https://syzkaller.appspot.com/bug?extid=6783b9aaa6a224fabde8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=140ddf93980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11c83909980000
Reported-by: syzbot+6783b9aaa6a224fabde8@syzkaller.appspotmail.com
Fixes: 24c5100aceed ("fs/ntfs3: Fix getting file type")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-08-30 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 16:51 [syzbot] [ntfs3?] INFO: trying to register non-static key in do_mpage_readpage (2) syzbot
2024-08-30 10:44 ` syzbot [this message]
2024-11-07 11:24 ` 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=00000000000001a0600620e4451b@google.com \
--to=syzbot+6783b9aaa6a224fabde8@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--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 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.