On 2017-08-08 09:15, David Laight wrote:
From: Pasha Tatashin
Sent: 08 August 2017 12:49
Thank you for looking at this change. What you described was in my
previous iterations of this project.
See for example here: https://lkml.org/lkml/2017/5/5/369
I was asked to remove that flag, and only zero memory in place when
needed. Overall the current approach is better everywhere else in the
kernel, but it adds a little extra code to kasan initialization.
Perhaps you could #define the function prototype(s?) so that the flags
are not passed unless it is a kasan build?
Hi David,
Thank you for suggestion. I think a kasan specific vmemmap (what I
described in the previous e-mail) would be a better solution over having
different prototypes with different builds. It would be cleaner to have
all kasan specific code in one place.
Pasha
--
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
