search for: prot_mt

...nately tagging granule-aligned symbols that fall in the right segments. i think a design that prevents sharing is not acceptable. > Unfortunately shared memory isn't required to be tag capable (DAX <https://www.kernel.org/doc/Documentation/filesystems/dax.txt> is an example) - so any PROT_MTE mappings must be anonymous. That's why we'd like to carve out rodata into its own segment, to continue to allow page sharing for the rest of the 80% of the stuff in that segment. static int a[8]; static int *p = a - 5; > ... > p[10] = 1; > should work (even if it's...

...granule size (16 bytes), resize to multiple of granule size (e.g. 40B -> 48B). 2. Ban data folding (except where contents and size are same, no tail merging). 3. In the loader, ensure writable segments (and possibly .rodata, see next dot point) are mapped MAP_ANONYMOUS and PROT_MTE (with the contents of the mappings filled from the file), as file-based mappings aren't necessarily backed by tag-capable memory. It also requires in-place remapping of data segments from the program image (as they're already mapped by the kernel before PT_INTERP invokes the lo...

...esize to multiple of granule size > (e.g. 40B -> 48B). > > > > Ban data folding (except where contents and size are same, no tail > merging). > > > > In the loader, ensure writable segments (and possibly .rodata, see next > dot point) are mapped MAP_ANONYMOUS and PROT_MTE (with the contents of the > mappings filled from the file), as file-based mappings aren't necessarily > backed by tag-capable memory. It also requires in-place remapping of data > segments from the program image (as they're already mapped by the kernel > before PT_INTERP invoke...

...of granule size (e.g. 40B -> 48B). >>> > >>> > Ban data folding (except where contents and size are same, no tail merging). >>> > >>> > In the loader, ensure writable segments (and possibly .rodata, see next dot point) are mapped MAP_ANONYMOUS and PROT_MTE (with the contents of the mappings filled from the file), as file-based mappings aren't necessarily backed by tag-capable memory. It also requires in-place remapping of data segments from the program image (as they're already mapped by the kernel before PT_INTERP invokes the loader). >&...