while this bug is still open, would it make sense to disable the gcc
option/optimization/bug/flaw that allows this vulnerability to exist?
the -fno-delete-null-pointer-checks flag will completely disable
this option kernel-wide [1].
obviously there is a tradeoff here. the null pointer
On Mon, Jul 20, 2009 at 12:09:05AM -0400, Michael S Gilbert wrote:
while this bug is still open, would it make sense to disable the gcc
option/optimization/bug/flaw that allows this vulnerability to exist?
the -fno-delete-null-pointer-checks flag will completely disable
this option kernel-wide
2 matches
Mail list logo
