From: syzbot <syzbot+63ba90b81c16b86379bd@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org,
almaz.alexandrovich@paragon-software.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] possible deadlock in gup_fast_fallback
Date: Wed, 24 Jul 2024 18:01:01 -0700 [thread overview]
Message-ID: <000000000000ae7466061e07ed39@google.com> (raw)
In-Reply-To: <0000000000006bca48061692b790@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=157ffac9980000
start commit: 786c8248dbd3 Merge tag 'perf-tools-fixes-for-v6.11-2024-07..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=177ffac9980000
console output: https://syzkaller.appspot.com/x/log.txt?x=137ffac9980000
kernel config: https://syzkaller.appspot.com/x/.config?x=d732ba79a3d0331b
dashboard link: https://syzkaller.appspot.com/bug?extid=63ba90b81c16b86379bd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=162862e3980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10d14ce3980000
Reported-by: syzbot+63ba90b81c16b86379bd@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-25 1:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 3:14 [syzbot] [mm?] possible deadlock in gup_fast_fallback syzbot
2024-07-24 14:10 ` syzbot
2024-07-25 1:01 ` 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=000000000000ae7466061e07ed39@google.com \
--to=syzbot+63ba90b81c16b86379bd@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.