From: syzbot <syzbot+c1751b6739d83d70bb75@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_mmap
Date: Sat, 27 Jul 2024 14:30:04 -0700 [thread overview]
Message-ID: <000000000000caad4b061e4154d2@google.com> (raw)
In-Reply-To: <0000000000002488fc061ae886f8@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=17772623980000
start commit: 2f8c4f506285 Merge tag 'auxdisplay-for-v6.11-tag1' of git:..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14f72623980000
console output: https://syzkaller.appspot.com/x/log.txt?x=10f72623980000
kernel config: https://syzkaller.appspot.com/x/.config?x=5efb917b1462a973
dashboard link: https://syzkaller.appspot.com/bug?extid=c1751b6739d83d70bb75
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=108328d9980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12e875a1980000
Reported-by: syzbot+c1751b6739d83d70bb75@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-07-27 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-15 7:17 [syzbot] [ntfs3?] possible deadlock in ntfs_file_mmap syzbot
2024-07-27 13:44 ` syzbot
2024-07-27 22:40 ` Hillf Danton
2024-07-27 23:03 ` syzbot
2024-07-27 21:30 ` 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=000000000000caad4b061e4154d2@google.com \
--to=syzbot+c1751b6739d83d70bb75@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