From: James Morris <jmorris@intercode.com.au>
To: Greg KH <greg@kroah.com>
Cc: Olaf Dietsche <olaf.dietsche#list.linux-kernel@t-online.de>,
<linux-security-module@wirex.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] LSM fix for stupid "empty" functions
Date: Tue, 3 Dec 2002 19:04:56 +1100 (EST) [thread overview]
Message-ID: <Mutt.LNX.4.44.0212031855220.27503-100000@blackbird.intercode.com.au> (raw)
In-Reply-To: <20021202065736.GA11477@kroah.com>
On Sun, 1 Dec 2002, Greg KH wrote:
> Anyway, there's no way to resolve both this percieved problem, and the
> "smaller and easier" patch that I proposed, right? Unless we want to
> export all dummy operation functions for all modules to use? I could do
> that, but it's pretty messy...
Yeah, very. I guess a security module could check the kernel version and
print a warning to the effect "this module has not been verified with this
kernel version" either at compile or runtime, if needed.
- James
--
James Morris
<jmorris@intercode.com.au>
next prev parent reply other threads:[~2002-12-03 7:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-01 8:30 Greg KH
2002-12-01 8:17 ` Crispin Cowan
2002-12-01 17:49 ` Greg KH
2002-12-01 16:59 ` Olaf Dietsche
2002-12-01 18:12 ` Greg KH
2002-12-01 17:21 ` Christoph Hellwig
2002-12-01 18:26 ` Greg KH
2002-12-03 2:37 ` Dragan Stancevic
2002-12-03 16:01 ` Greg KH
2002-12-03 15:14 ` Dragan Stancevic
2002-12-01 17:46 ` James Morris
2002-12-01 18:46 ` Olaf Dietsche
2002-12-01 20:05 ` Greg KH
2002-12-01 19:25 ` Greg KH
2002-12-02 2:00 ` James Morris
2002-12-02 6:57 ` Greg KH
2002-12-03 8:04 ` James Morris [this message]
2002-12-04 0:13 ` [RFC] LSM fix for stupid "empty" functions - take 2 Greg KH
2002-12-04 8:14 ` Chris Wright
2002-12-04 23:00 ` Greg KH
2002-12-04 23:44 ` Chris Wright
2002-12-05 0:09 ` James Morris
2002-12-01 18:57 [RFC] LSM fix for stupid "empty" functions Adam J. Richter
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=Mutt.LNX.4.44.0212031855220.27503-100000@blackbird.intercode.com.au \
--to=jmorris@intercode.com.au \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=olaf.dietsche#list.linux-kernel@t-online.de \
/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®