From: Arjan van de Ven <arjan@infradead.org>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: arjan@pentafluge.infradead.org, linux-kernel@vger.kernel.org,
akpm@osdl.org
Subject: Re: Add "FORTIFY_SOURCE" to the linux kernel
Date: Wed, 25 May 2005 16:47:16 +0200 [thread overview]
Message-ID: <1117032436.6010.76.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <4294891E.4070702@vc.cvut.cz>
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.
next prev parent reply other threads:[~2005-05-25 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 8:43 arjan
2005-05-25 14:18 ` Petr Vandrovec
2005-05-25 14:47 ` Arjan van de Ven [this message]
2005-05-25 15:40 ` Roman Zippel
2005-05-25 15:56 ` Arjan van de Ven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1117032436.6010.76.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=arjan@pentafluge.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®