linux-kernel - Workqueue behaviour - Synchronization within submitted work.

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-next>] [day] [month] [year] [list]

Message-ID: <CAEtk5ge3MBn5759EfUVdNRmb2g=kvtbe7u+xkZXy5E0KoynoJw@mail.gmail.com>
Date:	Wed, 20 Mar 2013 11:45:32 -0700
From:	Vijay <thelonejoker@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Workqueue behaviour - Synchronization within submitted work.

In the new workqueue architecture, I have a question regarding
synchronization between different "work" submitted to the same
workqueue. For example:

* I submit two "works" A and B to a common driver specific workqueue (W).
* Each A and B, meddle with a certain shared data SD.
* Am I guaranteed serialized execution of A and B, or should I play
safe and use a semaphore (acquire/release) with A and B ?

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