From: syzbot <syzbot+7736960b837908f3a81d@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org,
almaz.alexandrovich@paragon-software.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, nogikh@google.com, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com, willy@infradead.org
Subject: Re: [syzbot] [ntfs3?] possible deadlock in filemap_fault
Date: Wed, 03 Jan 2024 18:02:06 -0800 [thread overview]
Message-ID: <000000000000606eb4060e151e5f@google.com> (raw)
In-Reply-To: <0000000000008aa01105ec98487b@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=152a3829e80000
start commit: 610a9b8f49fb Linux 6.7-rc8
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=172a3829e80000
console output: https://syzkaller.appspot.com/x/log.txt?x=132a3829e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=655f8abe9fe69b3b
dashboard link: https://syzkaller.appspot.com/bug?extid=7736960b837908f3a81d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11013129e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12c68929e80000
Reported-by: syzbot+7736960b837908f3a81d@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
parent reply other threads:[~2024-01-04 2:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <0000000000008aa01105ec98487b@google.com>]
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=000000000000606eb4060e151e5f@google.com \
--to=syzbot+7736960b837908f3a81d@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=linux-mm@kvack.org \
--cc=nogikh@google.com \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).