From: syzbot <syzbot+d7452fc408a961bcc6ec@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 ntfs_file_write_iter
Date: Sat, 03 Aug 2024 01:04:03 -0700 [thread overview]
Message-ID: <00000000000028b122061ec2e3b9@google.com> (raw)
In-Reply-To: <00000000000078a6b2061ae9c05c@google.com>
syzbot has bisected this issue to:
commit 69505fe98f198ee813898cbcaf6770949636430b
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Thu May 30 07:54:07 2024 +0000
fs/ntfs3: Replace inode_trylock with inode_lock
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=135e0bbd980000
start commit: c0ecd6388360 Merge tag 'pci-v6.11-fixes-1' of git://git.ke..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=10de0bbd980000
console output: https://syzkaller.appspot.com/x/log.txt?x=175e0bbd980000
kernel config: https://syzkaller.appspot.com/x/.config?x=288f248fe2b6eab0
dashboard link: https://syzkaller.appspot.com/bug?extid=d7452fc408a961bcc6ec
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=142941a1980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15b302d9980000
Reported-by: syzbot+d7452fc408a961bcc6ec@syzkaller.appspotmail.com
Fixes: 69505fe98f19 ("fs/ntfs3: Replace inode_trylock with inode_lock")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-08-03 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-15 8:45 [syzbot] [ntfs3?] possible deadlock in ntfs_file_write_iter syzbot
2024-08-02 11:23 ` syzbot
2024-08-03 8:04 ` 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=00000000000028b122061ec2e3b9@google.com \
--to=syzbot+d7452fc408a961bcc6ec@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