linux-kernel - Synchronization mechanism between wait_for_completion_interruptible

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAG0bkvJvskLT5JMDwFhzoPNAajKnGauJ41w39E8N9RVc6Hi3mg@mail.gmail.com>
Date:	Wed, 4 Mar 2015 18:46:43 +0530
From:	Naveen Kumar Parna <pnaveenkos@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Synchronization mechanism between wait_for_completion_interruptible_timeout()
 & complete()

Hello,

I have a question regarding the synchronization mechanism between
wait_for_completion_interruptible_timeout() & complete(). I used
complete() API in the ISR Tx interrupt path and
wait_for_completion_interruptible_timeout() in struct file_operations
.write method.

Let assume a scenario in which Tx interrupt occurred and ISR called
complete() API before any process actually blocked at write method on
wait_for_completion_interruptible_timeout().

After a few milli seconds, a process called write() API. Does it gets
blocked on wait_for_completion_interruptible_timeout() for completion
of a specific task to be signaled from new Tx interrupt?

Thanks,
Naveen
--
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/