From: Denis Kenzior <denkenz@gmail.com>
To: iwd@lists.01.org
Subject: Re: [PATCH v2 2/3] rrm: add radio resource management module
Date: Wed, 06 Nov 2019 15:59:29 -0600 [thread overview]
Message-ID: <93b7533b-410b-0803-cd4a-e439d942af66@gmail.com> (raw)
In-Reply-To: <62ca199a1e05bc90e09f7469282ecafce8a3ca4a.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
Hi James,
>> Shouldn't you be checking that station exists first? Also, you have
>> a
>> bit of a chicken/egg problem since station is watching the same
>> netdev_watch. So by luck of the draw it may be getting notified
>> (and
>> thus created) after the rrm module.
>>
>> How we get around this is unclear. One way would be to check the
>> iftype
>> to be station and just assume that the station object comes around
>> eventually. Perhaps by lazy-instantiating the station watch only
>> once
>> an actual request arrives.
>
> What about adding a module depends on station? This would make RRM get
> initialized after station which should make the netdev watch call into
> station before RRM.
>
Possible, though that seems to be really unobvious. And if someone
changes watchlist to use push_head instead of push_tail, things start to
break.
Also, this is not really a module-initialization order issue but what
order does the watchlist get called issue. So it just seems like the
wrong way to go.
Perhaps we need an explicit API for when an interface gets added, or
just cheat and use delayed-init.
Regards,
-Denis
next prev parent reply other threads:[~2019-11-06 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 17:57 [PATCH v2 1/3] wiphy: add beacon bits to RM Enabled Capabilities James Prestwood
2019-11-06 17:57 ` [PATCH v2 2/3] rrm: add radio resource management module James Prestwood
2019-11-06 21:34 ` Denis Kenzior
2019-11-06 21:51 ` James Prestwood
2019-11-06 21:59 ` Denis Kenzior [this message]
2019-11-06 17:57 ` [PATCH v2 3/3] auto-t: add RRM autotest James Prestwood
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=93b7533b-410b-0803-cd4a-e439d942af66@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.01.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