From: syzbot <syzbot+33a67f9990381cc8951c@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?] BUG: unable to handle kernel paging request in attr_data_read_resident
Date: Wed, 19 Jul 2023 04:39:30 -0700 [thread overview]
Message-ID: <00000000000018e0570600d57cdb@google.com> (raw)
In-Reply-To: <0000000000007cfb2405febf9023@google.com>
syzbot has bisected this issue to:
commit ad26a9c84510af7252e582e811de970433a9758f
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Fri Oct 7 17:08:06 2022 +0000
fs/ntfs3: Fixing wrong logic in attr_set_size and ntfs_fallocate
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=143dfc66a80000
start commit: 74f1456c4a5f Merge tag 'linux-kselftest-fixes-6.5-rc3' of ..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=163dfc66a80000
console output: https://syzkaller.appspot.com/x/log.txt?x=123dfc66a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=77b9a3cf8f44c6da
dashboard link: https://syzkaller.appspot.com/bug?extid=33a67f9990381cc8951c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15619a3aa80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12288c1aa80000
Reported-by: syzbot+33a67f9990381cc8951c@syzkaller.appspotmail.com
Fixes: ad26a9c84510 ("fs/ntfs3: Fixing wrong logic in attr_set_size and ntfs_fallocate")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-07-19 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 22:39 [syzbot] [ntfs3?] BUG: unable to handle kernel paging request in attr_data_read_resident syzbot
2023-07-19 11:39 ` syzbot [this message]
2024-07-23 23:58 ` 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=00000000000018e0570600d57cdb@google.com \
--to=syzbot+33a67f9990381cc8951c@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.