Re: Add "FORTIFY_SOURCE" to the linux kernel

[Arjan van de Ven]

On Wed, 2005-05-25 at 16:18 +0200, Petr Vandrovec wrote:
> Hello,
>    how is this going to comply with rule that no existing symbols will be turned
> into GPLONLY symbols, as stated by Linus couple of time, and mentioned for example
> at http://www.tux.org/lkml/#s1-19 ?  To me it looks that no non-GPL module can work
> on such kernel anymore, as memcpy/strcpy/... functions now, although themselves non-GPL
> accessible (but inline...), depend on GPLONLY symbols.  Can you explain this to
> me?

then don't set the config option in your kernel, and you don't get
these. Also memcpy_chk() is not an existing function, it is a new one.
This is by no means mandatory.

Or, alternatively, in your module UNDEF the config option before
including these headers.


>    And if you think that it is right thing to do, would not it be simpler for
> everybody changing module loader so it just refuses to load non-GPL modules ?
> Final functionality would be same in both cases...

that is not correct.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/