linux-kernel - Re: Module/kthread/printk question/problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4F2969B7.4040202@linaro.org>
Date:	Wed, 01 Feb 2012 20:35:03 +0400
From:	Dmitry Antipov <dmitry.antipov@...aro.org>
To:	Eric Dumazet <eric.dumazet@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Module/kthread/printk question/problem

On 02/01/2012 08:31 PM, Eric Dumazet wrote:

> Race is here :
>
> Here you allow testmod_exit() to continue, while _this_ thread has not
> yet exited.
>
> And if this thread is preempted a litle bit, its code already was freed.
> ->  crash.

I realize this, but there was a second part of the question: what's the
better way to ensure that all test/X threads are really gone at some point of
testmod_exit()?

Thanks,
Dmitry

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/