Slides for my "Memory Tagging for the Kernel: Tag-Based KASAN" talk at Android Security Symposium:
Conversation
Replying to
From what I can hear the only issue with software based tagging is that you have to make sure you control all the allocation systems? (I.E. so they don't malloc(huge) and then do internal things to it?) Or did I get confused?
1
Replying to
The only issue in what sense? Hardware memory tagging won't be able to handle the custom allocators (malloc(huge)) properly too. But there will be no need to rebuild the code itself, you only need to change allocator.
Replying to
Only issue in terms of getting proper coverage for bugfinding, was what I was thinking? It was a great ppt btw.
1
Replying to
Thanks! Re coverage: with the software approach you can only cover whatever you have the source code for and you can rebuild; with hardware - closed-source binary only stuff should also be coverable (as long as it's using the allocator under your control)
1