From: Johannes Berg <johannes@sipsolutions.net>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: syzbot <syzbot+18c783c5cf6a781e3e2c@syzkaller.appspotmail.com>,
linux-wireless@vger.kernel.org, ramonreisfontes@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in __ieee80211_beacon_get
Date: Wed, 16 Aug 2023 23:04:52 +0200 [thread overview]
Message-ID: <3e34b44f06a7b21a6148bec8750ebc3d4e78b284.camel@sipsolutions.net> (raw)
In-Reply-To: <CANp29Y7TVNRFpcN1qSSurwWAtbBn90z_eUet3UdOcdDdUZ7zrg@mail.gmail.com>
On Wed, 2023-08-16 at 21:56 +0200, Aleksandr Nogikh wrote:
> >
> > Is there an easy way to rebuild the kernel for it?
>
> How does an easy way differ from a difficult one in this case? :)
>
:-)
I was mostly thinking about "how the hell do I get the kernel into the
qemu image" but I realized later I don't even need to since qemu has the
-kernel option to boot the kernel directly.
Then I had to leave for a while so I only got to try it now, and indeed
I can reproduce it with a kernel built/booted that way, so I can make
changes for debugging. In fact, not even sure what else I really need
from the rootfs at that point, but this is still an easy way to
reproduce it.
Sorry for the noise.
johannes
next prev parent reply other threads:[~2023-08-16 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 8:38 WARNING in __ieee80211_beacon_get syzbot
2023-08-16 8:09 ` Johannes Berg
2023-08-16 13:39 ` Aleksandr Nogikh
2023-08-16 14:01 ` Johannes Berg
2023-08-16 19:56 ` Aleksandr Nogikh
2023-08-16 21:04 ` Johannes Berg [this message]
2023-08-17 11:15 ` 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=3e34b44f06a7b21a6148bec8750ebc3d4e78b284.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nogikh@google.com \
--cc=ramonreisfontes@gmail.com \
--cc=syzbot+18c783c5cf6a781e3e2c@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.