From: syzbot <syzbot+38f5d5cf7ae88c46b11a@syzkaller.appspotmail.com>
To: a@unstable.cc, b.a.t.m.a.n@lists.open-mesh.org,
davem@davemloft.net, gregkh@linuxfoundation.org,
hdanton@sina.com, hongjiefang@asrmicro.com,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
longman@redhat.com, mareklindner@neomailbox.ch, mingo@kernel.org,
netdev@vger.kernel.org, peterz@infradead.org,
sw@simonwunderlich.de, syzkaller-bugs@googlegroups.com,
tj@kernel.org, ulf.hansson@linaro.org
Subject: Re: WARNING in kernfs_create_dir_ns
Date: Wed, 15 Apr 2020 17:11:03 -0700 [thread overview]
Message-ID: <000000000000ba8e5605a35d4465@google.com> (raw)
In-Reply-To: <0000000000003ec128058c7624ec@google.com>
syzbot suspects this bug was fixed by commit:
commit 810507fe6fd5ff3de429121adff49523fabb643a
Author: Waiman Long <longman@redhat.com>
Date: Thu Feb 6 15:24:08 2020 +0000
locking/lockdep: Reuse freed chain_hlocks entries
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1008138be00000
start commit: 72825454 Merge branch 'x86-urgent-for-linus' of git://git...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=9a31528e58cc12e2
dashboard link: https://syzkaller.appspot.com/bug?extid=38f5d5cf7ae88c46b11a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12a6c439a00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1353c323a00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: locking/lockdep: Reuse freed chain_hlocks entries
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-04-16 0:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 13:12 WARNING in kernfs_create_dir_ns syzbot
2019-06-30 5:41 ` syzbot
2019-07-08 14:46 ` Tejun Heo
2019-06-30 10:40 ` syzbot
2020-04-16 0:11 ` syzbot [this message]
2020-04-16 0:30 ` Waiman Long
[not found] <20190709022335.12928-1-hdanton@sina.com>
2019-07-09 14:22 ` Tejun Heo
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=000000000000ba8e5605a35d4465@google.com \
--to=syzbot+38f5d5cf7ae88c46b11a@syzkaller.appspotmail.com \
--cc=a@unstable.cc \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=hongjiefang@asrmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mareklindner@neomailbox.ch \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sw@simonwunderlich.de \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
--cc=ulf.hansson@linaro.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 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.