On 11/20/2017 12:41 AM, Dmitry Vyukov wrote:
The reason I didn't submit the vchecker to mainline is that I didn't find
the case that this tool is useful in real life. Most of the system broken case
can be debugged by other ways. Do you see the real case that this tool is
helpful?
Hi,
Yes, this is the main question here.
How is it going to be used in real life? How widely?
I think the owner check can be enabled in the cases where KASAN is used.
-- That is that we found there is memory issue, but don't know how it
happened.
It's not the first hit of problem -- no production system will run with
KASAN enabled, KASAN is performance killer. And the use case is that we
found the overwritten happened on some particular victims, we then want
to add owner check on those victims.
thanks,
wengang
If so, I think that vchecker is more appropriate to be upstreamed.
Could you share your opinion?
Thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
