From: syzbot <syzbot+28207acc70bbf3d85b74@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?] BUG: unable to handle kernel paging request in mi_enum_attr
Date: Sat, 04 Feb 2023 05:56:16 -0800 [thread overview]
Message-ID: <00000000000067d34605f3e029f7@google.com> (raw)
In-Reply-To: <000000000000f61bdf05e79a7c5c@google.com>
syzbot suspects this issue was fixed by commit:
commit 0e8235d28f3a0e9eda9f02ff67ee566d5f42b66b
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Mon Oct 10 10:15:33 2022 +0000
fs/ntfs3: Check fields while reading
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13c11ba5480000
start commit: f9ff5644bcc0 Merge tag 'hsi-for-6.2' of git://git.kernel.o..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=c163713cf9186fe7
dashboard link: https://syzkaller.appspot.com/bug?extid=28207acc70bbf3d85b74
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1275aed7880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=124f533b880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs/ntfs3: Check fields while reading
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-02-04 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 9:46 [syzbot] BUG: unable to handle kernel paging request in mi_enum_attr syzbot
2022-10-22 11:43 ` syzbot
2023-02-04 13:56 ` syzbot [this message]
2023-02-06 10:09 ` [syzbot] [ntfs3?] " Aleksandr Nogikh
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=00000000000067d34605f3e029f7@google.com \
--to=syzbot+28207acc70bbf3d85b74@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