From: Jiri Pirko <jiri@resnulli.us>
To: syzbot <syzbot+896295c817162503d359@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, jiri@mellanox.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in devlink_get_from_attrs
Date: Mon, 7 Oct 2019 21:11:02 +0200 [thread overview]
Message-ID: <20191007191102.GD2326@nanopsycho> (raw)
In-Reply-To: <000000000000b11343059456a5f5@google.com>
Mon, Oct 07, 2019 at 08:59:11PM CEST, syzbot+896295c817162503d359@syzkaller.appspotmail.com wrote:
>Hello,
>
>syzbot found the following crash on:
>
>HEAD commit: 056ddc38 Merge branch 'stmmac-next'
>git tree: net-next
>console output: https://syzkaller.appspot.com/x/log.txt?x=1590218f600000
>kernel config: https://syzkaller.appspot.com/x/.config?x=d9be300620399522
>dashboard link: https://syzkaller.appspot.com/bug?extid=896295c817162503d359
>compiler: gcc (GCC) 9.0.0 20181231 (experimental)
>syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10a6a6c3600000
>C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15fd50dd600000
>
>IMPORTANT: if you fix the bug, please add the following tag to the commit:
>Reported-by: syzbot+896295c817162503d359@syzkaller.appspotmail.com
>
>kasan: CONFIG_KASAN_INLINE enabled
>kasan: GPF could be caused by NULL-ptr deref or user memory access
>general protection fault: 0000 [#1] PREEMPT SMP KASAN
>CPU: 1 PID: 8790 Comm: syz-executor447 Not tainted 5.4.0-rc1+ #0
>Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
>Google 01/01/2011
>RIP: 0010:devlink_get_from_attrs+0x32/0x300 net/core/devlink.c:124
This is fixed already by:
5c23afb980b2 ("net: devlink: fix reporter dump dumpit")
next prev parent reply other threads:[~2019-10-07 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 18:59 general protection fault in devlink_get_from_attrs syzbot
2019-10-07 19:11 ` Jiri Pirko [this message]
2019-10-07 19:16 ` Eric Biggers
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=20191007191102.GD2326@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=jiri@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+896295c817162503d359@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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).