From: David Miller <davem@davemloft.net>
To: syzbot+8da67f407bcba2c72e6e@syzkaller.appspotmail.com
Cc: andy@greyhouse.net, j.vosburgh@gmail.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, vfalico@gmail.com,
ap420073@gmail.com
Subject: Re: INFO: trying to register non-static key in bond_3ad_update_ad_actor_settings
Date: Mon, 28 Oct 2019 21:24:49 -0700 (PDT) [thread overview]
Message-ID: <20191028.212449.1389218373993746531.davem@davemloft.net> (raw)
In-Reply-To: <000000000000929f990596024a82@google.com>
From: syzbot <syzbot+8da67f407bcba2c72e6e@syzkaller.appspotmail.com>
Date: Mon, 28 Oct 2019 18:11:08 -0700
> syzbot has found a reproducer for the following crash on:
>
> HEAD commit: 60c1769a Add linux-next specific files for 20191028
> git tree: linux-next
> console output:
> https://syzkaller.appspot.com/x/log.txt?x=154d4374e00000
> kernel config:
> https://syzkaller.appspot.com/x/.config?x=cb86688f30db053d
> dashboard link:
> https://syzkaller.appspot.com/bug?extid=8da67f407bcba2c72e6e
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14d43a04e00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16be3b9ce00000
>
> IMPORTANT: if you fix the bug, please add the following tag to the
> commit:
> Reported-by: syzbot+8da67f407bcba2c72e6e@syzkaller.appspotmail.com
This might be because of the lockdep depth changes.
Taehee, please take a look.
Thanks.
next prev parent reply other threads:[~2019-10-29 4:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 17:18 INFO: trying to register non-static key in bond_3ad_update_ad_actor_settings syzbot
2019-10-29 1:11 ` syzbot
2019-10-29 4:24 ` David Miller [this message]
2019-10-29 5:09 ` Taehee Yoo
2019-10-29 9:52 ` syzbot
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=20191028.212449.1389218373993746531.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=ap420073@gmail.com \
--cc=j.vosburgh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+8da67f407bcba2c72e6e@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vfalico@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 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).