[lkml]   [2022]   [Jul]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v8] ath9k: let sleep be interrupted when unregistering hwrng
On 07/07/22 19:26, Kalle Valo wrote:
> "Jason A. Donenfeld" <> writes:
>> There are two deadlock scenarios that need addressing, which cause
>> problems when the computer goes to sleep, the interface is set down, and
>> hwrng_unregister() is called. When the deadlock is hit, sleep is delayed
>> for tens of seconds, causing it to fail. These scenarios are:
>> 1) The hwrng kthread can't be stopped while it's sleeping, because it
>> uses msleep_interruptible() instead of schedule_timeout_interruptible().
>> The fix is a simple moving to the correct function. At the same time,
>> we should cleanup a common and useless dmesg splat in the same area.
>> 2) A normal user thread can't be interrupted by hwrng_unregister() while
>> it's sleeping, because hwrng_unregister() is called from elsewhere.
>> The solution here is to keep track of which thread is currently
>> reading, and asleep, and signal that thread when it's time to
>> unregister. There's a bit of book keeping required to prevent
>> lifetime issues on current.
>> Reported-by: Gregory Erwin <>
>> Cc: Toke Høiland-Jørgensen <>
>> Cc: Kalle Valo <>
>> Cc: Rui Salvaterra <>
>> Cc: Herbert Xu <>
>> Cc:
>> Fixes: fcd09c90c3c5 ("ath9k: use hw_random API instead of directly dumping into random.c")
>> Link:
>> Link:
>> Link:
>> Signed-off-by: Jason A. Donenfeld <>
>> ---
>> Changes v7->v8:
>> - Add a missing export_symbol.
>> drivers/char/hw_random/core.c | 30 ++++++++++++++++++++++++----
>> drivers/net/wireless/ath/ath9k/rng.c | 19 +++++++-----------
>> kernel/sched/core.c | 1 +
>> 3 files changed, 34 insertions(+), 16 deletions(-)
> I don't see any acks for the hw_random and the scheduler change, adding more
> people to CC. Full patch here:
> Are everyone ok if I take this patch via wireless-next?

Thanks for the Cc.

I'm not hot on the export of wake_up_state(), IMO any wakeup with
!(state & TASK_NORMAL) should be reserved to kernel internals. Now, here
IIUC the problem is that the patch uses an inline invoking

wake_up_state(p, TASK_INTERRUPTIBLE)

so this isn't playing with any 'exotic' task state, thus it shouldn't
actually need the export.

I've been trying to figure out if this could work with just a
wake_up_process(), but the sleeping pattern here is not very conforming
(cf. 'wait loop' pattern in sched/core.c), AFAICT the signal is used to
circumvent that :/

 \ /
  Last update: 2022-07-11 13:46    [W:0.094 / U:0.888 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site