From: syzbot <syzbot+e27980339d305f2dbfd9@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, hughd@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org
Subject: Re: possible deadlock in shmem_mfill_atomic_pte
Date: Sat, 11 Apr 2020 01:52:03 -0700 [thread overview]
Message-ID: <000000000000b61fcf05a2fff6ed@google.com> (raw)
In-Reply-To: <000000000000571acf05a229cb2f@google.com>
syzbot has bisected this bug to:
commit 71725ed10c40696dc6bdccf8e225815dcef24dba
Author: Hugh Dickins <hughd@google.com>
Date: Tue Apr 7 03:07:57 2020 +0000
mm: huge tmpfs: try to split_huge_page() when punching hole
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17c463e7e00000
start commit: ab6f762f printk: queue wake_up_klogd irq_work only if per-..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=142463e7e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=102463e7e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=3010ccb0f380f660
dashboard link: https://syzkaller.appspot.com/bug?extid=e27980339d305f2dbfd9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12d3c5afe00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15e7f51be00000
Reported-by: syzbot+e27980339d305f2dbfd9@syzkaller.appspotmail.com
Fixes: 71725ed10c40 ("mm: huge tmpfs: try to split_huge_page() when punching hole")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-04-11 8:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 17:21 possible deadlock in shmem_mfill_atomic_pte syzbot
2020-04-11 5:16 ` syzbot
2020-04-16 3:56 ` Yang Shi
2020-04-16 6:58 ` syzbot
2020-04-11 8:52 ` syzbot [this message]
2020-04-13 23:19 ` Yang Shi
2020-04-16 1:27 ` Hugh Dickins
2020-04-16 2:22 ` Yang Shi
2020-04-16 3:10 ` Hugh Dickins
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=000000000000b61fcf05a2fff6ed@google.com \
--to=syzbot+e27980339d305f2dbfd9@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).