[lkml]   [2018]   [Mar]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC PATCH v19 0/8] mm: security: ro protection for dynamic data
On 13/03/18 23:45, Igor Stoppa wrote:


Some more thoughts about the open topics:

> Discussion topics that are unclear if they are closed and would need
> comment from those who initiated them, if my answers are accepted or not:
> * @Kees Cook proposed to have first self testing for genalloc, to
> validate the following patch, adding tracing of allocations
> My answer was that such tests would also need patching, therefore they
> could not certify that the functionality is corect both before and
> after the genalloc bitmap modification.

This is the only one where I still couldn't find a solution.
If Matthew Wilcox's proposal about implementing the the genalloc bitmap
would work, then this too could be done, but I think this alternate
bitmap proposed has problems. More on it below.

> * @Kees Cook proposed to turn the self testing into modules.
> My answer was that the functionality is intentionally tested very early
> in the boot phase, to prevent unexplainable errors, should the feature
> really fail.

This could be workable, if it's acceptable that the early testing is
performed only when the module is compiled in.
I do not expect the module-based testing to bring much value, but it
doesn't do harm. Is this acceptable?

> * @Matthew Wilcox proposed to use a different mechanism for the genalloc
> bitmap: 2 bitmaps, one for occupation and one for start.
> And possibly use an rbtree for the starts.
> My answer was that this solution is less optimized, because it scatters
> the data of one allocation across multiple words/pages, plus is not
> a transaction anymore. And the particular distribution of sizes of
> allocation is likely to eat up much more memory than the bitmap.

I think I can describe a scenario where the split bitmaps would not work
(based on my understanding of the proposal), but I would appreciate a
review. Here it is:

* One allocation (let's call it allocation A) is already present in both
- its units of allocation are marked in the "space" bitmap
- its starting bit is marked in the "starts" bitmap

* Another allocation (let's call it allocation B) is undergoing:
- some of its units of allocation (starting from the beginning) are
marked in the "space" bitmap
- the starting bit is *not* yet marked in the "starts" bitmap

* B occupies the space immediately after A

* While B is being written, A is freed

* Having to determine the length of A, the "space" bitmap will be
searched, then the "starts" bitmap

The space initially allocated for B will be wrongly accounted for A,
because there is no empty gap in-between and the beginning of B is not
yet marked.

The implementation which interleaves "space" and "start" does not suffer
from this sort of races, because the alteration of the interleaved
bitmaps is atomic.

However, at the very least, some more explanation is needed in the
documentation/code, because this scenario is not exactly obvious.

Does this justification for the use of interleaved bitmaps (iow the
current implementation) make sense?


 \ /
  Last update: 2018-03-14 12:23    [W:0.142 / U:3.928 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site