Emmanuel Grumbach wrote: > It is not really my business, but how come this happen with ath9k? > The scan should be cancelled before the interface is removed. You mean > that the scan cancellation is > asynchronous and the notification of the cancellation termination can > come after the cfg80211 has removed > the interface?
Yes, the scan cancellation is initiated on interface removal, but it's async. These commits explain the race: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/net/wireless/core.c?id=a617302c531eaf497ccd02a61d380efc119ba999 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/net/wireless/core.c?id=f9d15d162b3acf28f85b3ac05c4883e5ed588d28 We see it often with ath9k on a low-powered board, with a 'state manager' that plays with the interfaces. Sujith -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
