You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read your paper and it impressed me very much. However, I am still confused about "shadow objects" introduced in your paper.
First, as said in the paper, shadow objects is a work-around of hardware isolation mechanism as its protection unit (page) may contain both distinguishing and non-distinguishing regions. However, since a page is 4KB, is it rare that a page only contains distinguishing regions? In other words, is all the distinguishing regions need to be protected with shadow objects?
Second, you create a shadow slab for each slab and guarantee that each object has the same offset to the page where it is stored on the original slab and shadow slab, is this means for each kmalloc call you have to allocate a shadow object no matter if it belongs to distinguishing regions because the offset would be wrong otherwise?
Third, the write operation to distinguishing regions on the heap will be redirected to shadow objects, so will you update the data of shadow objects to the original objects? if not so, I think read operations would get wrong answers.
The text was updated successfully, but these errors were encountered:
Hi,
I have read your paper and it impressed me very much. However, I am still confused about "shadow objects" introduced in your paper.
First, as said in the paper, shadow objects is a work-around of hardware isolation mechanism as its protection unit (page) may contain both distinguishing and non-distinguishing regions. However, since a page is 4KB, is it rare that a page only contains distinguishing regions? In other words, is all the distinguishing regions need to be protected with shadow objects?
Second, you create a shadow slab for each slab and guarantee that each object has the same offset to the page where it is stored on the original slab and shadow slab, is this means for each kmalloc call you have to allocate a shadow object no matter if it belongs to distinguishing regions because the offset would be wrong otherwise?
Third, the write operation to distinguishing regions on the heap will be redirected to shadow objects, so will you update the data of shadow objects to the original objects? if not so, I think read operations would get wrong answers.
The text was updated successfully, but these errors were encountered: