Thread (25 messages) 25 messages, 3 authors, 2019-08-02

Re: [PATCH v3] kasan: add memory corruption identification for software tag-based mode

From: Walter Wu <hidden>
Date: 2019-08-02 03:04:30
Also in: linux-mediatek, linux-mm, lkml

On Wed, 2019-07-31 at 20:04 +0300, Andrey Ryabinin wrote:
On 7/26/19 4:19 PM, Walter Wu wrote:
quoted
On Fri, 2019-07-26 at 15:52 +0300, Andrey Ryabinin wrote:
quoted
On 7/26/19 3:28 PM, Walter Wu wrote:
quoted
On Fri, 2019-07-26 at 15:00 +0300, Andrey Ryabinin wrote:
quoted
quoted
quoted

I remember that there are already the lists which you concern. Maybe we
can try to solve those problems one by one.

1. deadlock issue? cause by kmalloc() after kfree()?
smp_call_on_cpu()
quoted
quoted
2. decrease allocation fail, to modify GFP_NOWAIT flag to GFP_KERNEL?
No, this is not gonna work. Ideally we shouldn't have any allocations there.
It's not reliable and it hurts performance.
I dont know this meaning, we need create a qobject and put into
quarantine, so may need to call kmem_cache_alloc(), would you agree this
action?
How is this any different from what you have now?
I originally thought you already agreed the free-list(tag-based
quarantine) after fix those issue. If no allocation there,
If no allocation there, than it must be somewhere else.
We known exactly the amount of memory we need, so it's possible to preallocate it in advance.
I see. We will implement an extend slub to record five free backtrack
and free pointer tag, and determine whether it is oob or uaf by the free
pointer tag. If you have other ideas, please tell me. Thanks.

 


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help