Le 21/08/2018 à 14:49, Greg Troxel a écrit :
Maxime Villard writes:
Here is a patch [1] that allows kasan to monitor pools and pool_caches. We
recycle the existing POOL_REDZONE implementation - which I wrote three years
ago, and which has never been enabled (not even on DEBUG). With this we
On Aug 21, 2:30pm, m...@m00nbsd.net (Maxime Villard) wrote:
-- Subject: Re: kasan: monitor pools
| Why not, but origsize will become unused, so still need one ifdef.
Yes, I've left the ifdef, instead of __kasanused :-)
christos
On Aug 21, 1:17pm, campbell+netbsd-tech-k...@mumble.net (Taylor R Campbell)
wrote:
-- Subject: Re: kasan: monitor pools
| Make it a static inline with empty body instead of a #define
| __nothing?
Because i don't want the parameters to have to exist (be declared)
or be evaluated... I want them
> Date: Tue, 21 Aug 2018 14:30:55 +0200
> From: Maxime Villard
>
> Le 21/08/2018 à 14:05, Christos Zoulas a écrit :
> > Sure, how about also following the empty function style the redzone code
> > follows to reduce ifdefs?
>
> Why not, but origsize will become unused, so still need one ifdef.
Le 21/08/2018 à 14:05, Christos Zoulas a écrit :
In article <2a4c7cde-ab5e-68b7-de0f-0a307e91a...@m00nbsd.net>,
Maxime Villard wrote:
Here is a patch [1] that allows kasan to monitor pools and pool_caches. We
recycle the existing POOL_REDZONE implementation - which I wrote three years
ago,
In article <2a4c7cde-ab5e-68b7-de0f-0a307e91a...@m00nbsd.net>,
Maxime Villard wrote:
>Here is a patch [1] that allows kasan to monitor pools and pool_caches. We
>recycle the existing POOL_REDZONE implementation - which I wrote three years
>ago, and which has never been enabled (not even on
Here is a patch [1] that allows kasan to monitor pools and pool_caches. We
recycle the existing POOL_REDZONE implementation - which I wrote three years
ago, and which has never been enabled (not even on DEBUG). With this we can
detect read/write buffer overflows on all our pools, and in
