From: Hans de Goede <hdegoede@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>,
"Peer, Ilan" <ilan.peer@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Coelho, Luciano" <luciano.coelho@intel.com>
Subject: Re: pull-request: mac80211 2021-01-18.2
Date: Mon, 25 Jan 2021 13:59:03 +0100 [thread overview]
Message-ID: <92c434bd-bf79-2b49-2a0a-8e538d55551c@redhat.com> (raw)
In-Reply-To: <671b0c37867803d7229ef0c4a33baf2c7778df08.camel@sipsolutions.net>
Hi,
On 1/25/21 1:40 PM, Johannes Berg wrote:
> Hi,
>
>>> I don't have that much sympathy for a staging driver that's clearly
>>> doing things differently than it was intended (the documentation states
>>> that the function should be called only before wiphy_register(), not
>>> during ndo_open). :-)
>>
>> I completely understand and I already was worried that this might be
>> a staging-driver issue, which is why I mentioned this was with a
>> staging driver in the more detailed bug-report email.
>
> I guess I missed that, but no worries.
>
>>> But OTOH, that fix to the driver is simple and looks correct to me since
>>> it only ever has a static regdomain, and the notifier does the work of
>>> applying it to the channels as well.
>>
>> So I've given your fix a quick try and it leads to a NULL pointer deref.
>
> Ouch. Oh. I see, that driver is *really* stupid, trying to get to the
> wiphy from the adapter, but going through the wdev instead ... ouch.
>
> Wow are these pointers a mess in that driver ... Something like this,
> perhaps?
>
> https://p.sipsolutions.net/4400d9a3b7b800bb.txt
Yes this fixes things, thank you that saves me from having to debug
the NULL ptr deref.
Do you want to submit this to Greg, or shall I (I've already
added it to me local tree as a commit with you as the author) ?
If you want me to submit it upstream, may I have / add your S-o-b
for this ?
Regards,
Hans
next prev parent reply other threads:[~2021-01-26 5:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 20:47 pull-request: mac80211 2021-01-18.2 Johannes Berg
2021-01-18 22:50 ` patchwork-bot+netdevbpf
2021-01-20 17:59 ` Johannes Berg
2021-01-20 20:37 ` Jakub Kicinski
2021-01-20 20:39 ` Johannes Berg
2021-01-23 21:31 ` Hans de Goede
2021-01-23 22:15 ` Johannes Berg
2021-01-24 9:12 ` Peer, Ilan
2021-01-24 10:54 ` Hans de Goede
2021-01-24 13:03 ` Peer, Ilan
2021-01-25 9:47 ` Johannes Berg
2021-01-25 11:18 ` Hans de Goede
2021-01-25 12:40 ` Johannes Berg
2021-01-25 12:59 ` Hans de Goede [this message]
2021-01-25 13:03 ` 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=92c434bd-bf79-2b49-2a0a-8e538d55551c@redhat.com \
--to=hdegoede@redhat.com \
--cc=ilan.peer@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=netdev@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