From: syzbot <syzbot+65684128cd7c35bc66a1@syzkaller.appspotmail.com>
To: cgroups@vger.kernel.org, davem@davemloft.net, hannes@cmpxchg.org,
johan.hedberg@gmail.com, keescook@chromium.org, kennyyu@fb.com,
kuba@kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, lizefan@huawei.com,
luto@amacapital.net, marcel@holtmann.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tj@kernel.org, wad@chromium.org
Subject: Re: inconsistent lock state in sco_conn_del
Date: Sat, 12 Sep 2020 05:59:07 -0700 [thread overview]
Message-ID: <000000000000e5419905af1d5d2b@google.com> (raw)
In-Reply-To: <0000000000004991e705ac9d1a83@google.com>
syzbot has bisected this issue to:
commit 135b8b37bd91cc82f83e98fca109b80375f5317e
Author: Kenny Yu <kennyyu@fb.com>
Date: Tue Jun 21 18:04:36 2016 +0000
cgroup: Add pids controller event when fork fails because of pid limit
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12f6d80d900000
start commit: e8878ab8 Merge tag 'spi-fix-v5.9-rc4' of git://git.kernel...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=11f6d80d900000
console output: https://syzkaller.appspot.com/x/log.txt?x=16f6d80d900000
kernel config: https://syzkaller.appspot.com/x/.config?x=c61610091f4ca8c4
dashboard link: https://syzkaller.appspot.com/bug?extid=65684128cd7c35bc66a1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=121ef0fd900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16c3a853900000
Reported-by: syzbot+65684128cd7c35bc66a1@syzkaller.appspotmail.com
Fixes: 135b8b37bd91 ("cgroup: Add pids controller event when fork fails because of pid limit")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-09-12 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 17:07 inconsistent lock state in sco_conn_del syzbot
2020-09-12 1:35 ` syzbot
2020-09-12 12:59 ` syzbot [this message]
2020-10-10 9:14 Xu, Yanfei
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=000000000000e5419905af1d5d2b@google.com \
--to=syzbot+65684128cd7c35bc66a1@syzkaller.appspotmail.com \
--cc=cgroups@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=hannes@cmpxchg.org \
--cc=johan.hedberg@gmail.com \
--cc=keescook@chromium.org \
--cc=kennyyu@fb.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=luto@amacapital.net \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
--cc=wad@chromium.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).