From: Greg KH <greg@kroah.com>
To: James Morris <jmorris@intercode.com.au>
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: Sun, 1 Dec 2002 22:57:37 -0800 [thread overview]
Message-ID: <20021202065736.GA11477@kroah.com> (raw)
In-Reply-To: <Mutt.LNX.4.44.0212021248290.20929-100000@blackbird.intercode.com.au>
On Mon, Dec 02, 2002 at 01:00:27PM +1100, James Morris wrote:
> On Sun, 1 Dec 2002, Greg KH wrote:
>
> > > I think we still want to make sure that the module author has explicitly
> > > accounted for all of the hooks, in case new hooks are added.
> >
> > But with this patch, if the module author hasn't specified a hook, they
> > get the "dummy" ones. So the structure should always be full of
> > pointers, making the VERIFY_STRUCT macro pointless.
>
> Yes, but defaulting unspecified hooks to dummy operations could be
> dangerous. A module might appear to compile and run perfectly well, but
> be missing some important new hook.
One could argue that a "important new hook" would provide a sane dummy
operation, or that if the module doesn't need it, why would it want to
provide it? :)
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...
thanks,
greg k-h
next prev parent reply other threads:[~2002-12-02 5:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-01 8:30 [RFC] LSM fix for stupid "empty" functions 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 [this message]
2002-12-03 8:04 ` James Morris
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
-- strict thread matches above, loose matches on Subject: below --
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=20021202065736.GA11477@kroah.com \
--to=greg@kroah.com \
--cc=jmorris@intercode.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.