diff options
| author | Johannes Berg <johannes@sipsolutions.net> | 2009-08-21 14:51:05 +0200 |
|---|---|---|
| committer | John W. Linville <linville@tuxdriver.com> | 2009-08-28 14:40:31 -0400 |
| commit | 3d54d25515838543e56889aa7e48f40d00719368 (patch) | |
| tree | ac8e7ab50b5fa9e9be64885f86c99a0b6c71892c /arch | |
| parent | f7969969f416e593bcc7dc24abf3f9fd6c27136d (diff) | |
cfg80211: clean up properly on interface type change
When the interface type changes while connected, and the
driver does not require the interface to be down for a
type change, it is currently possible to get very strange
results unless the driver takes special care, which it
shouldn't have to.
To fix this, take care to disconnect/leave IBSS when
changing the interface type -- even if the driver may fail
the call. Also process all events that may be pending to
avoid running into a situation where an event is reported
but only processed after the type has already changed,
which would lead to missing events and warnings.
A side effect of this is that you will have disconnected
or left the IBSS even if the mode change ultimately fails,
but since the intention was to change it and thus leave or
disconnect, this is not a problem.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions