From: syzbot <syzbot+913093197c71922e8375@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
clang-built-linux@googlegroups.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, nathan@kernel.org,
ndesaulniers@google.com, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com, trix@redhat.com
Subject: Re: [syzbot] [ntfs3?] INFO: task hung in ntfs_read_folio (2)
Date: Sat, 28 Oct 2023 10:05:05 -0700 [thread overview]
Message-ID: <000000000000743d980608c9ce33@google.com> (raw)
In-Reply-To: <0000000000003ba9f506013b0aed@google.com>
syzbot suspects this issue was fixed by commit:
commit bfbe5b31caa74ab97f1784fe9ade5f45e0d3de91
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Fri Jun 30 12:22:53 2023 +0000
fs/ntfs3: fix deadlock in mark_as_free_ex
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14006f67680000
start commit: bfa3037d8280 Merge tag 'fuse-update-6.5' of git://git.kern..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=a4507c291b5ab5d4
dashboard link: https://syzkaller.appspot.com/bug?extid=913093197c71922e8375
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15b8869ea80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=149e6072a80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs/ntfs3: fix deadlock in mark_as_free_ex
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-10-28 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 12:49 [syzbot] [ntfs3?] INFO: task hung in ntfs_read_folio (2) syzbot
2023-07-29 6:45 ` syzbot
2023-10-28 17:05 ` 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=000000000000743d980608c9ce33@google.com \
--to=syzbot+913093197c71922e8375@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trix@redhat.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 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).