From: James Prestwood <prestwoj@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [RFC 0/1] Hwsim crash when receiving cloned frame
Date: Thu, 10 Sep 2020 16:57:06 -0700 [thread overview]
Message-ID: <20200910235707.7732-1-prestwoj@gmail.com> (raw)
I am unsure if this is the proper way to fix this problem since it
ends up just dropping the frame when this happens. If 'channel'
*should* be initialized by the time we are receiving frames then
there may be a race somewhere. If its functionally ok for 'channel'
to be NULL, then maybe this fix is alright.
I realize it had been suggested to provide a decoded crash with
a debuggable kernel, but I really dont see how that could provide
any additional information above what is here. Because of this I
sent as an RFC and we can discuss further if needed.
James Prestwood (1):
mac80211_hwsim: fix crash when receiving frame
drivers/net/wireless/mac80211_hwsim.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.26.2
next reply other threads:[~2020-09-10 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 23:57 James Prestwood [this message]
2020-09-10 23:57 ` [RFC 1/1] mac80211_hwsim: fix crash when receiving frame James Prestwood
2020-09-17 9:46 ` 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=20200910235707.7732-1-prestwoj@gmail.com \
--to=prestwoj@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/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).