From: syzbot <syzbot+adf6c6c2be1c3a718121@syzkaller.appspotmail.com>
To: aarcange@redhat.com, akpm@linux-foundation.org,
coreteam@netfilter.org, davem@davemloft.net, fw@strlen.de,
kadlec@netfilter.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
pablo@netfilter.org, syzkaller-bugs@googlegroups.com,
torvalds@linux-foundation.org, xiyou.wangcong@gmail.com
Subject: Re: INFO: task hung in hashlimit_mt_check_common
Date: Sat, 25 Jan 2020 23:26:01 -0800 [thread overview]
Message-ID: <0000000000001d2faa059d05e738@google.com> (raw)
In-Reply-To: <000000000000466b64059bcb3843@google.com>
syzbot has bisected this bug to:
commit 7ddd8faf4399ab4f4edad5604eab35f8a87caf02
Author: Andrea Arcangeli <aarcange@redhat.com>
Date: Fri Oct 13 22:57:54 2017 +0000
userfaultfd: selftest: exercise -EEXIST only in background transfer
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=175625c9e00000
start commit: 8f8972a3 Merge tag 'mtd/fixes-for-5.5-rc7' of git://git.ke..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=14d625c9e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=10d625c9e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=d9290aeb7e6cf1c4
dashboard link: https://syzkaller.appspot.com/bug?extid=adf6c6c2be1c3a718121
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14ea2559e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15ffc8bee00000
Reported-by: syzbot+adf6c6c2be1c3a718121@syzkaller.appspotmail.com
Fixes: 7ddd8faf4399 ("userfaultfd: selftest: exercise -EEXIST only in background transfer")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-01-26 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 16:00 INFO: task hung in hashlimit_mt_check_common syzbot
2020-01-19 8:17 ` syzbot
2020-01-26 7:26 ` syzbot [this message]
[not found] ` <20200126132352.8212-1-hdanton@sina.com>
2020-02-01 7:05 ` Dan Carpenter
2020-02-01 18:52 ` Cong Wang
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=0000000000001d2faa059d05e738@google.com \
--to=syzbot+adf6c6c2be1c3a718121@syzkaller.appspotmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=xiyou.wangcong@gmail.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.