Netdev List
 help / color / mirror / Atom feed
From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+3640e696903873858f7e@syzkaller.appspotmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: WARNING: CPU: 1
Date: Mon, 28 Sep 2020 12:46:08 +0200	[thread overview]
Message-ID: <0e2bbc76-1451-a084-dc16-b21c33ca6d82@broadcom.com> (raw)
In-Reply-To: <CACT4Y+ZkwMZ3Bu77WGtmOGihNbgspdicEq5d_LA1hDVL=KkZyA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1852 bytes --]

On 9/28/2020 12:04 PM, Dmitry Vyukov wrote:
> On Mon, Sep 28, 2020 at 11:31 AM Arend Van Spriel
> <arend.vanspriel@broadcom.com> wrote:
>>
>> On 9/27/2020 10:47 AM, Dmitry Vyukov wrote:
>>> On Sun, Sep 27, 2020 at 10:38 AM syzbot
>>> <syzbot+3640e696903873858f7e@syzkaller.appspotmail.com> wrote:
>>>>
>>>> Hello,
>>>>
>>>> syzbot found the following issue on:
>>>>
>>>> HEAD commit:    748d1c8a Merge branch 'devlink-Use-nla_policy-to-validate-..
>>>> git tree:       net-next
>>>> console output: https://syzkaller.appspot.com/x/log.txt?x=13ac3ec3900000
>>>> kernel config:  https://syzkaller.appspot.com/x/.config?x=51fb40e67d1e3dec
>>>> dashboard link: https://syzkaller.appspot.com/bug?extid=3640e696903873858f7e
>>>> compiler:       gcc (GCC) 10.1.0-syz 20200507
>>>> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1599be03900000
>>>> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=149fd44b900000
>>>
>>> Based on the reproducer, this looks like some wireless bug.
>>> +net/wireless maintainers.
>>
>> I don't think so looking at this part of the stacktrace:
>>
>> [   51.814941]  [<ffffffff8465cc95>] macvlan_common_newlink+0xa15/0x1720
>> [   51.833542]  [<ffffffff84662548>] macvtap_newlink+0x128/0x230
>> [   51.858008]  [<ffffffff85b68bfe>] rtnl_newlink+0xe5e/0x1780
>> [   51.925885]  [<ffffffff85b5d32b>] rtnetlink_rcv_msg+0x22b/0xc20
>>
>> Regards,
>> Arend
> 
> That's the trace on the oldest release and the bisection was diverged
> somewhere midway.
> You may see this in the bisection log:
> https://syzkaller.appspot.com/text?tag=Log&x=1474aaad900000
> 
> Initially it crashed with this warning:
> all runs: crashed: WARNING in sta_info_insert_rcu
> 
> This function is in net/mac80211/sta_info.c.

I see. Thanks for the clarification. It was not really obvious where to 
dig for information.

Regards,
Arend

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4176 bytes --]

  reply	other threads:[~2020-09-28 10:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-27  8:38 WARNING: CPU: 1 syzbot
2020-09-27  8:47 ` Dmitry Vyukov
2020-09-28  9:30   ` Arend Van Spriel
2020-09-28 10:04     ` Dmitry Vyukov
2020-09-28 10:46       ` Arend Van Spriel [this message]
2021-01-05 10:18       ` Dmitry Vyukov

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=0e2bbc76-1451-a084-dc16-b21c33ca6d82@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=dvyukov@google.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+3640e696903873858f7e@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