# Is there a realistic scenario where the mask passed to doRemoteMaskOp is the current core?

**URL:** <https://sel4.discourse.group/t/is-there-a-realistic-scenario-where-the-mask-passed-to-doremotemaskop-is-the-current-core/621>\
**Category:** seL4 kernel\
**Created:** [November 22, 2022, 9:55am UTC](https://sel4.discourse.group/t/is-there-a-realistic-scenario-where-the-mask-passed-to-doremotemaskop-is-the-current-core/621 "2022-11-22T09:55:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jack.Chen](https://avatars.discourse-cdn.com/v4/letter/j/c68b51/32.png) [@Jack.Chen](https://sel4.discourse.group/u/Jack.Chen)\
**Post date:** [November 22, 2022, 9:55am UTC](https://sel4.discourse.group/t/is-there-a-realistic-scenario-where-the-mask-passed-to-doremotemaskop-is-the-current-core/621/1 "2022-11-22T09:55:13Z")

</div>

It seems like the “current core **IS** set in the mask” situation in doRemoteMaskOp can’t really be created with the 12.1.0-release kernel without any modifications (i.e., fault injection). Is it an l4v-related safety measure or is there actually a realistic condition that leads to this situation?

Also, the comment in the code seems to suggest such a precondition, but I have hard time making sense of it.

```auto
    /* this may happen, e.g. the caller tries to map a pagetable in
    * newly created PD which has not been run yet. Guard against them! */
    if (mask != 0) {

```