From: Guenter Roeck <linux@roeck-us.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: syzbot <syzbot+684d4ca200fda0b2141e@syzkaller.appspotmail.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] upstream boot error: general protection fault in nl80211_put_iface_combinations
Date: Tue, 16 Aug 2022 08:33:45 -0700 [thread overview]
Message-ID: <20220816153345.GA2905014@roeck-us.net> (raw)
In-Reply-To: <6a7b0bc82647440a9036a8e637807da618552cc5.camel@sipsolutions.net>
On Tue, Aug 16, 2022 at 05:11:32PM +0200, Johannes Berg wrote:
> Hmm.
>
> > HEAD commit: 568035b01cfb Linux 6.0-rc1
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=145d8a47080000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=126b81cc3ce4f07e
> >
>
> I can't reproduce this, and I don't see anything obviously wrong with
> the code there in hwsim either.
>
> Similarly with
> https://syzkaller.appspot.com/bug?extid=655209e079e67502f2da
>
> Anyone have any ideas what to do next?
>
Ignore it. It is caused by a problem in virtio. See revert series at
https://lore.kernel.org/lkml/20220816053602.173815-1-mst@redhat.com/
Guenter
> johannes
next prev parent reply other threads:[~2022-08-16 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 8:37 [syzbot] upstream boot error: general protection fault in nl80211_put_iface_combinations syzbot
2022-08-16 15:11 ` Johannes Berg
2022-08-16 15:33 ` Guenter Roeck [this message]
2022-08-16 15:34 ` Johannes Berg
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=20220816153345.GA2905014@roeck-us.net \
--to=linux@roeck-us.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+684d4ca200fda0b2141e@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 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.