From: syzbot <syzbot+c986d2a447ac6fb27b02@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ntfs3@lists.linux.dev, pjwatson999@gmail.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [ntfs3?] KASAN: use-after-free Read in hdr_find_e
Date: Wed, 01 Feb 2023 06:55:23 -0800 [thread overview]
Message-ID: <00000000000047848f05f3a4a32f@google.com> (raw)
In-Reply-To: <000000000000fea8c705e9a732af@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=1268739e480000
start commit: 55be6084c8e0 Merge tag 'timers-core-2022-10-05' of git://g..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=df75278aabf0681a
dashboard link: https://syzkaller.appspot.com/bug?extid=c986d2a447ac6fb27b02
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=164e92a4880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=126f7ac6880000
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-01 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 11:46 [syzbot] KASAN: use-after-free Read in hdr_find_e syzbot
2022-09-29 3:19 ` syzbot
2023-02-01 14:55 ` syzbot [this message]
2023-02-02 7:00 ` [syzbot] [ntfs3?] " Dmitry Vyukov
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=00000000000047848f05f3a4a32f@google.com \
--to=syzbot+c986d2a447ac6fb27b02@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=pjwatson999@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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.