From: Dongliang Mu <mudongliangabcd@gmail.com>
To: xiaoqiang zhao <zhaoxiaoqiang007@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Kalle Valo <kvalo@codeaurora.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Luca Coelho <luciano.coelho@intel.com>,
Ilan Peer <ilan.peer@intel.com>,
syzbot+1638e7c770eef6b6c0d0@syzkaller.appspotmail.com,
Johannes Berg <johannes.berg@intel.com>,
linux-wireless@vger.kernel.org,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: free the object allocated in wiphy_apply_custom_regulatory
Date: Fri, 23 Jul 2021 17:44:03 +0800 [thread overview]
Message-ID: <CAD-N9QXdv2me8wSm0D9nN72j3oP8mc5vsLJ+ffbH2fbCS6_F_A@mail.gmail.com> (raw)
In-Reply-To: <2e9e6fa7-a405-088d-3b4c-da62b85f3fc6@gmail.com>
On Fri, Jul 23, 2021 at 5:36 PM xiaoqiang zhao
<zhaoxiaoqiang007@gmail.com> wrote:
>
>
>
> 在 2021/7/23 17:25, Dongliang Mu 写道:
> > Can you point out the concrete code releasing regd? Maybe the link to elixir.
> >
> >>> ieee80211_unregister_hw(data->hw);
> >>> device_release_driver(data->dev);
> >>> device_unregister(data->dev);
> >>>
>
> call graph seems like this:
>
> ieee80211_unregister_hw
> (https://elixir.bootlin.com/linux/v5.14-rc2/source/net/mac80211/main.c#L1368)
> wiphy_unregister
> (https://elixir.bootlin.com/linux/v5.14-rc2/source/net/wireless/core.c#L1011)
> wiphy_regulatory_deregister
> (https://elixir.bootlin.com/linux/v5.14-rc2/source/net/wireless/reg.c#L4057)
> rcu_free_regdom
Thanks very much. This is really helpful.
>
prev parent reply other threads:[~2021-07-23 9:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 5:09 [PATCH] cfg80211: free the object allocated in wiphy_apply_custom_regulatory Dongliang Mu
2021-07-23 5:16 ` Dongliang Mu
2021-07-23 8:37 ` Johannes Berg
2021-07-23 9:13 ` Dongliang Mu
2021-07-23 9:18 ` Johannes Berg
2021-07-23 9:30 ` Dongliang Mu
2021-07-23 9:42 ` Johannes Berg
2021-07-23 9:59 ` Dongliang Mu
2021-07-23 9:18 ` xiaoqiang zhao
2021-07-23 9:25 ` Dongliang Mu
2021-07-23 9:36 ` xiaoqiang zhao
2021-07-23 9:44 ` Dongliang Mu [this message]
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=CAD-N9QXdv2me8wSm0D9nN72j3oP8mc5vsLJ+ffbH2fbCS6_F_A@mail.gmail.com \
--to=mudongliangabcd@gmail.com \
--cc=davem@davemloft.net \
--cc=ilan.peer@intel.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=netdev@vger.kernel.org \
--cc=syzbot+1638e7c770eef6b6c0d0@syzkaller.appspotmail.com \
--cc=zhaoxiaoqiang007@gmail.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 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).