linux-kernel - Re: wait_for_completion

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: <1172763563.25580.5.camel@mtls03>
Date:	Thu, 01 Mar 2007 17:39:23 +0200
From:	Eli Cohen <eli@...lanox.co.il>
To:	Dmitry Adamushko <dmitry.adamushko@...il.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: wait_for_completion_timeout problem ???

On Thu, 2007-03-01 at 16:14 +0100, Dmitry Adamushko wrote:

> Mea culpa. Don't know why I took it as 10 ms.. Yep, in case of seconds
> it rather becomes a mere theoretical possibility.
> 
> Are you sure there are no other "waiters" being blocked on the same
> "completion" at the same time? complete_all()?
> 
> Anyway, do "cat /proc/your_task_pid/status" and look at the "State: "
> field. It should be "R" in case wake_up_*() was called for this task.
> 

Thanks for your good advices. Right now it seems that increasing the
timeout to 60 sec did the trick :-)
The test I was running has many threads and maybe there is starvation of
tasks. The system is also not too responsive to say the least.
-
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/