From: Greg KH <greg@kroah.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, linux-staging@lists.linux.dev,
Harald Arnesen <harald@skogtun.org>
Subject: Re: [PATCH] staging: rtl8723bs: fix monitor netdev register/unregister
Date: Tue, 27 Apr 2021 11:03:32 +0200 [thread overview]
Message-ID: <YIfTZKtMcMAB2e4k@kroah.com> (raw)
In-Reply-To: <aad26597fc709dd67bf010b60590120148bc16c6.camel@sipsolutions.net>
On Tue, Apr 27, 2021 at 10:53:58AM +0200, Johannes Berg wrote:
> On Tue, 2021-04-27 at 08:25 +0200, Greg KH wrote:
> >
> > > +++ b/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
> > > @@ -2579,7 +2579,7 @@ static int rtw_cfg80211_add_monitor_if(struct adapter *padapter, char *name, str
> > > mon_wdev->iftype = NL80211_IFTYPE_MONITOR;
> > > mon_ndev->ieee80211_ptr = mon_wdev;
> > >
> > > - ret = register_netdevice(mon_ndev);
> > > + ret = cfg80211_register_netdevice(mon_ndev);
> >
> > Is this now a requirement for all wireless drivers?
>
> Yes and no. It must only be called from within a "please add an
> interface" method. Otherwise, register_netdevice() must still be called.
>
> > If so, do other drivers/staging/ drivers need to also be fixed up?
>
> Not as far as I can tell, this is the only wireless staging driver that
> even calls register_netdevice(). Not sure why I missed this, I had
> audited all of those calls across the tree. But looking a second time
> always shows more I guess, sorry about that.
>
> There's another call to register_netdevice() here but I don't think
> that's affected, however, it's obviously utterly broken in the first
> place:
>
> if (!rtnl_is_locked())
> unregister_netdev(cur_pnetdev);
> else
> unregister_netdevice(cur_pnetdev);
>
> *sigh*.
Sorry, these staging wireless drivers are really getting annoying.
Maybe I need to turn an intern onto them to just get them fixed up and
out of here to be a 'real' driver.
> > I'm guessing this will be going through the wireless tree, so:
> >
> > Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> I don't care much, since unfortunately it's already too late and the
> breakage is released in 5.12. I'll pick it up through my tree since I
> broke it (and probably should add a Cc stable tag.)
Great, thanks for taking it that way and doing this fix, much
appreciated.
greg k-h
next prev parent reply other threads:[~2021-04-27 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 19:28 [PATCH] staging: rtl8723bs: fix monitor netdev register/unregister Johannes Berg
2021-04-27 6:25 ` Greg KH
2021-04-27 8:53 ` Johannes Berg
2021-04-27 9:03 ` Greg KH [this message]
2021-04-27 9:04 ` 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=YIfTZKtMcMAB2e4k@kroah.com \
--to=greg@kroah.com \
--cc=harald@skogtun.org \
--cc=johannes@sipsolutions.net \
--cc=linux-staging@lists.linux.dev \
--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).