On Thu, Oct 04, 2018 at 04:52:19PM +0800, Jia-Ju Bai wrote:
On 2018/10/4 15:59, Stanislaw Gruszka wrote:<snip>
On Wed, Oct 03, 2018 at 10:07:45PM +0800, Jia-Ju Bai wrote:My runtime testing shows that il4965_send_rxon_assoc() and
These possible races are detected by a runtime testing.Really ? I'm surprised by that, see below.
To fix these races, the mutex lock is used in il4965_send_rxon_assoc()
to protect the data.
il4965_configure_filter() are concurrently executed.
But after seeing your reply, I need to carefully check whether my
runtime testing is right, because I think you are right.
In fact, I only monitored the iwl4965 driver, but did not monitor
the iwlegacy driver, so I will do the testing again with monitoring
the lwlegacy driver.
So how those runtime test were performend such you didn'tSo I wonder how this patch did not cause the deadlock ?Oh, sorry, anyway, my patch will cause double locks...
notice this ?
Care to post a patch ?Anyway what can be done is adding:I agree.
lockdep_assert_held(&il->mutex);
il4965_commit_rxon() to check if we hold the mutex.