From: syzbot <syzbot+3f7f291a3d327486073c@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
gautammenghani201@gmail.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] KASAN: out-of-bounds Write in end_buffer_read_sync
Date: Sat, 06 Aug 2022 13:48:07 -0700 [thread overview]
Message-ID: <000000000000309f9e05e598b315@google.com> (raw)
In-Reply-To: <0000000000005b04fa05dd71e0e0@google.com>
syzbot has bisected this issue to:
commit 6e5be40d32fb1907285277c02e74493ed43d77fe
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Fri Aug 13 14:21:30 2021 +0000
fs/ntfs3: Add NTFS3 in fs/Kconfig and fs/Makefile
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14aab3ca080000
start commit: 200e340f2196 Merge tag 'pull-work.dcache' of git://git.ker..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=16aab3ca080000
console output: https://syzkaller.appspot.com/x/log.txt?x=12aab3ca080000
kernel config: https://syzkaller.appspot.com/x/.config?x=a3f4d6985d3164cd
dashboard link: https://syzkaller.appspot.com/bug?extid=3f7f291a3d327486073c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15e211fa080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14866761080000
Reported-by: syzbot+3f7f291a3d327486073c@syzkaller.appspotmail.com
Fixes: 6e5be40d32fb ("fs/ntfs3: Add NTFS3 in fs/Kconfig and fs/Makefile")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-08-06 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 3:07 [syzbot] KASAN: out-of-bounds Write in end_buffer_read_sync syzbot
2022-05-07 13:27 ` syzbot
2022-08-06 20:48 ` syzbot [this message]
2024-08-20 1:51 ` [syzbot] [ntfs3?] " 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=000000000000309f9e05e598b315@google.com \
--to=syzbot+3f7f291a3d327486073c@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=gautammenghani201@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.