The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: torvalds@transmeta.com, greg@kroah.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] make LSM register functions GPLonly exports
Date: Thu, 17 Oct 2002 15:35:05 +0100	[thread overview]
Message-ID: <20021017153505.A27998@infradead.org> (raw)

These exports have the power to change the implementations of all
syscalls and I've seen people exploiting this "feature".

Make the exports GPLonly (which some LSM folks agreed to
when it was merged initially to avoid that).

--- 1.2/security/security.c	Wed Aug 28 22:52:56 2002
+++ edited/security/security.c	Thu Oct 17 16:30:40 2002
@@ -241,9 +241,9 @@
 	return security_ops->sys_security (id, call, args);
 }
 
-EXPORT_SYMBOL (register_security);
-EXPORT_SYMBOL (unregister_security);
-EXPORT_SYMBOL (mod_reg_security);
-EXPORT_SYMBOL (mod_unreg_security);
-EXPORT_SYMBOL (capable);
-EXPORT_SYMBOL (security_ops);
+EXPORT_SYMBOL_GPL(register_security);
+EXPORT_SYMBOL_GPL(unregister_security);
+EXPORT_SYMBOL_GPL(mod_reg_security);
+EXPORT_SYMBOL_GPL(mod_unreg_security);
+EXPORT_SYMBOL(capable);
+EXPORT_SYMBOL(security_ops);

             reply	other threads:[~2002-10-17 14:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17 14:35 Christoph Hellwig [this message]
2002-10-17 15:07 ` [PATCH] make LSM register functions GPLonly exports Greg KH
2002-10-17 15:13   ` Christoph Hellwig
2002-10-17 16:21   ` Jeff Garzik
2002-10-17 16:51   ` Crispin Cowan
2002-10-17 16:54     ` Christoph Hellwig
2002-10-17 17:08       ` Linus Torvalds
2002-10-17 17:20         ` Greg KH
2002-10-17 17:25         ` Linus Torvalds
2002-10-17 20:39           ` Ingo Molnar
2002-10-17 17:44         ` Crispin Cowan
2002-10-17 18:03           ` Arjan van de Ven
2002-10-17 17:20       ` Richard B. Johnson
2002-10-17 17:26         ` Linus Torvalds

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=20021017153505.A27998@infradead.org \
    --to=hch@infradead.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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