Re: feature request: use optional memory option code for per process only memory, on newer linux kernels

[Lawrence Velázquez]

On Sat, Oct 9, 2021, at 7:04 PM, Alex fxmbsw7 Ratchev wrote:
> i sadly cant find any hint about it in my bookmarks or history, i think
> googles bug that is
> i think it was in the news about releaee notes for 5.14
> it was a BIG_CASE mem tag flag to use
>
> [for 5.16 futex2 may be sheduled, good for ipc]
>
> How does this differ from memory that's allocated the old-fashioned way?
>>
>
> it just as far i read but may not be limited to, mark allocated memory by
> kernel interface only accessable by own process ( dunno if its just that )
> that makes the whole sound more secure
> id use it everywhere
> but yea i dunno, there are no benefits for syses without this feature
> but i think its a very major feature coding facilities shouldnt miss
>
> How would you propose that bash make use of it?  What benefits does it
>> offer?  What would bash do on other platforms where this feature does
>> not exist?
>>
>
> i dunno either how would be implented, and dunno if for all or just parts
> user specified
> 'own_map' or something

So you don't know what this feature is called, don't have any links
for others to look into, can't really explain what it does, and
can't justify why bash would benefit from it, but you'd definitely
use it everywhere and think that bash (and everyone else) should
too?  Are you serious?

-- 
vq