From: syzbot <syzbot+af224b63e76b2d869bc3@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org,
almaz.alexandrovich@paragon-software.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
neilb@suse.de, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org
Subject: Re: [syzbot] [ntfs3?] general protection fault in ni_readpage_cmpr
Date: Tue, 21 Nov 2023 07:58:05 -0800 [thread overview]
Message-ID: <00000000000005f3f6060aabab28@google.com> (raw)
In-Reply-To: <000000000000b0cabf05f90bcb15@google.com>
syzbot suspects this issue was fixed by commit:
commit 013ff63b649475f0ee134e2c8d0c8e65284ede50
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Fri Jun 30 12:17:02 2023 +0000
fs/ntfs3: Add more attributes checks in mi_enum_attr()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14b8bcbf680000
start commit: 1b29d271614a Merge tag 'staging-6.4-rc7' of git://git.kern..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ac246111fb601aec
dashboard link: https://syzkaller.appspot.com/bug?extid=af224b63e76b2d869bc3
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1241fd03280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1476e8f3280000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs/ntfs3: Add more attributes checks in mi_enum_attr()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-11-21 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 9:05 [syzbot] [ntfs3?] general protection fault in ni_readpage_cmpr syzbot
2023-05-07 10:30 ` syzbot
2023-06-11 22:17 ` syzbot
2023-11-21 15:58 ` 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=00000000000005f3f6060aabab28@google.com \
--to=syzbot+af224b63e76b2d869bc3@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
/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.