[grsec] 'charp' module parameter, 2.1.14-2.6.31.5-200910312135

[pageexec at freemail.hu]

On 9 Nov 2009 at 9:11, hooanon05 at yahoo.co.jp wrote:

> I can modify my module to set the kfree-able memory to the module
> parameter, but it never fix the generic problem in grsecurity patch.
> I am afraid that the grsecurity patch has to choose Rusty Russell's
> memory-leak way until all modules fix their charp parameter.

since 31.6 includes this solution, i decided to leave it as it is, it's good
enough for PaX as it doesn't trip over the read-only memory enforcement which
is really what i cared about.