linux-kernel - Re: Any lightweight way for one thread to force another thread to suspend execution?

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: <e2e108260806210938k4ba12874t5f46e524ee188ab3@mail.gmail.com>
Date:	Sat, 21 Jun 2008 18:38:24 +0200
From:	"Bart Van Assche" <bart.vanassche@...il.com>
To:	"Eric Smith" <eric@...uhaha.com>
Cc:	linux-kernel@...r.kernel.org, "Andi Kleen" <andi@...stfloor.org>
Subject: Re: Any lightweight way for one thread to force another thread to suspend execution?

On Sat, Jun 21, 2008 at 1:54 AM, Eric Smith <eric@...uhaha.com> wrote:
> Is there any method for one thread to force another thread to suspend
> execution, then later let it resume, that is lighter weight than using
> signals?  I don't need it to be portable to anything other than Linux.
> The suspend needs to be synchronous, but resume doesn't.

Trying to suspend another thread synchronously is a bad idea because
this can easily trigger deadlocks. E.g. if you suspend a thread while
that thread holds a lock on a mutex, your application will deadlock.

Bart.
--
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/