From: syzbot <syzbot+8ef76b0b1f86c382ad37@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, anton@tuxera.com,
brauner@kernel.org, david@fromorbit.com, linkinjeon@kernel.org,
linux-kernel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com, willy@infradead.org
Subject: Re: [syzbot] [ntfs3?] possible deadlock in ntfs_read_folio
Date: Fri, 12 Jul 2024 10:10:02 -0700 [thread overview]
Message-ID: <0000000000003e26e7061d0ff386@google.com> (raw)
In-Reply-To: <0000000000001e3b8505e9f95e3d@google.com>
syzbot suspects this issue was fixed by commit:
commit 7ffa8f3d30236e0ab897c30bdb01224ff1fe1c89
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date: Mon Jan 15 07:20:25 2024 +0000
fs: Remove NTFS classic
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17bc0ea5980000
start commit: 2a6526c4f389 Merge tag 'linux_kselftest-kunit-fixes-6.8-rc..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=b0b9993d7d6d1990
dashboard link: https://syzkaller.appspot.com/bug?extid=8ef76b0b1f86c382ad37
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=117f19fde80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16ceb0cbe80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs: Remove NTFS classic
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-07-12 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 13:48 [syzbot] possible deadlock in ntfs_read_folio syzbot
2024-07-12 17:10 ` 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=0000000000003e26e7061d0ff386@google.com \
--to=syzbot+8ef76b0b1f86c382ad37@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=anton@tuxera.com \
--cc=brauner@kernel.org \
--cc=david@fromorbit.com \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--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