From: syzbot <syzbot+731b27ee9413ba859499@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] possible deadlock in run_unpack_ex
Date: Fri, 20 Dec 2024 14:26:03 -0800 [thread overview]
Message-ID: <6765eefb.050a0220.226966.0000.GAE@google.com> (raw)
In-Reply-To: <672dbfef.050a0220.69327.0000.GAE@google.com>
syzbot has bisected this issue to:
commit 5fc982fe7eca9d0cf7b25832450ebd4f7c8e1c36
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Thu Oct 10 17:09:24 2024 +0000
fs/ntfs3: Fix case when unmarked clusters intersect with zone
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17286fe8580000
start commit: baaa2567a712 Merge tag 'mmc-v6.13-rc2' of git://git.kernel..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14a86fe8580000
console output: https://syzkaller.appspot.com/x/log.txt?x=10a86fe8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1234f097ee657d8b
dashboard link: https://syzkaller.appspot.com/bug?extid=731b27ee9413ba859499
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11660fe8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12ce62df980000
Reported-by: syzbot+731b27ee9413ba859499@syzkaller.appspotmail.com
Fixes: 5fc982fe7eca ("fs/ntfs3: Fix case when unmarked clusters intersect with zone")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-12-20 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 7:38 [syzbot] [ntfs3?] possible deadlock in run_unpack_ex syzbot
2024-12-20 2:51 ` syzbot
2024-12-20 22:26 ` 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=6765eefb.050a0220.226966.0000.GAE@google.com \
--to=syzbot+731b27ee9413ba859499@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox