Searched full:confinement (Results 1 – 25 of 127) sorted by relevance
123456
59 For any surface, only one lock or confinement may be active across all60 wl_pointer objects of the same seat. If a lock or confinement is requested61 when another lock or confinement is active or requested on the same surface158 specific constraints are satisfied, the pointer confinement will be163 in order for the confinement to activate. It is up to the compositor165 the confinement to activate. If the region is null the surface input169 to interact with the confinement as well as receive updates about its180 <arg name="lifetime" type="uint" enum="lifetime" summary="confinement lifetime"/>274 This object will send the event 'confined' when the confinement is275 activated. Whenever the confinement is activated, it is guaranteed that[all …]
11 * [Thread confinement fine-grained](#thread-confinement-fine-grained)12 * [Thread confinement coarse-grained](#thread-confinement-coarse-grained)216 ### Thread confinement fine-grained273 This code works very slowly, because it does _fine-grained_ thread-confinement. Each individual inc…277 ### Thread confinement coarse-grained279 In practice, thread confinement is performed in large chunks, e.g. big pieces of state-updating bus…515 a coroutine and a coroutine is executed sequentially, so confinement of the state to the specific c…
115 …name='thread-confinement-fine-grained'></a>[Thread confinement fine-grained](docs/shared-mutable-s…116 …me='thread-confinement-coarse-grained'></a>[Thread confinement coarse-grained](docs/shared-mutable…
4 This application allows you to browse SELinux confinement per application. You can enter the name …
18 confinement: strict
11 confinement: devmode # use 'strict' once you have the right plugs and slots
21 confinement: strict
3 ## Subgroup confinement attacks35 subgroup confinement attacks. Without a key validation it is insecure to use the key-pair
22 confinement: strict
231 * should be rejected to prevent subgroup confinement attacks.
64 * subgroup confinement attacks. Without a key validation it is insecure to use the key-pair
1423 * To reduce thread contention and also to correctly handle thread-confinement1434 // and also solve thread confinement) in runWorkers()
3998 "confinement."
4003 "confinement."
3997 "confinement."