From: syzbot <syzbot+8df514c431bd240c5644@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] possible deadlock in mark_as_free_ex (2)
Date: Sat, 17 Jan 2026 04:45:01 -0800 [thread overview]
Message-ID: <696b844d.050a0220.3390f1.000b.GAE@google.com> (raw)
In-Reply-To: <672dbff0.050a0220.69327.0002.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit bcbb8d0afd94927215e8ae97c40cfefa807cfe0b
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Thu Oct 30 20:51:09 2025 +0000
fs/ntfs3: change the default mount options for "acl" and "prealloc"
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12e7739a580000
start commit: c9cfc122f037 Merge tag 'for-6.18-rc4-tag' of git://git.ker..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=41ad820f608cb833
dashboard link: https://syzkaller.appspot.com/bug?extid=8df514c431bd240c5644
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=114e4a58580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10bfc084580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs/ntfs3: change the default mount options for "acl" and "prealloc"
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2026-01-17 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 7:38 [syzbot] [ntfs3?] possible deadlock in mark_as_free_ex (2) syzbot
2024-11-29 1:43 ` syzbot
2024-12-12 8:35 ` syzbot
2024-12-13 9:05 ` [PATCH] ntfs3: fix deadlock in mark_as_free_ex Lizhi Xu
2024-12-13 6:43 ` [syzbot] [ntfs3?] possible deadlock in mark_as_free_ex (2) syzbot
2026-01-17 12:45 ` 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=696b844d.050a0220.3390f1.000b.GAE@google.com \
--to=syzbot+8df514c431bd240c5644@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox