public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastian Blank <bastian@waldi.eu.org>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] builtin stack support
Date: Fri, 20 Jun 2003 21:50:51 +0200	[thread overview]
Message-ID: <20030620195051.GA28020@wavehammer.waldi.eu.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1547 bytes --]

hi folks

the following patch
- modifies the security modules registering code to built a stack of
  modules themself
- changes the internal interface of the security functions to get a
  pointer to that stack
- the dummy functions always traverse through the stack
- register the dummy functions as a special security module
- drop the cap_* declaration
- drop mod_(un)reg_security
- add a name parameter to (un)register_security

missing things
- register_security isn't called, it may decide if it allowes the other
  module to be stacked together.

advantages
- it is possible to stack modules together without special support by
  the modules
- add functions which will be handled by a non standard module without
  need to modify the standard one

problems
- abi change, change of the security inline functions
- root_plug is currently unbuildable because the exports of the cap_*
  functions are dropped, it don't need to use them directly
- if the modules don't define a function, the call always travers
  through the stack until it hits the dummy module
- more pointer needs to be dereferences, more parameter

future enhancements
- define different stacks for different types of functions (may be
  faster)

i currently write a kernel extension which needs a security module
themself and i want to be able to load this module regardless of the
actual loaded modules.

i know that the patch is large, it needs to change one thing many times.

bastian

-- 
Captain's Log, star date 21:34.5...

[-- Attachment #1.2: diff.gz --]
[-- Type: application/octet-stream, Size: 14248 bytes --]

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2003-06-20 19:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-20 19:50 Bastian Blank [this message]
2003-06-20 23:36 ` [PATCH] builtin stack support Greg KH
2003-06-21  0:46   ` Crispin Cowan

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=20030620195051.GA28020@wavehammer.waldi.eu.org \
    --to=bastian@waldi.eu.org \
    --cc=linux-kernel@vger.kernel.org \
    /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