netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: James Morris <jmorris@namei.org>
Cc: netdev@vger.kernel.org, selinux@tycho.nsa.gov,
	davem@davemloft.net, sds@epoch.ncsc.mil, jmorris@redhat.com,
	pratt@argus-systems.com
Subject: Re: [PATCH 3/7] NetLabel: CIPSOv4 engine
Date: Sat, 15 Jul 2006 11:03:48 -0400	[thread overview]
Message-ID: <200607151103.49142.paul.moore@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0607142209180.19821@d.namei>

On Friday 14 July 2006 10:18 pm, James Morris wrote:
>
> If you're in a permanent cleanup phase, why bother clearing all of these
> global variables and using temporary pointers?
>
> Why not just simply free each entry?  The way this is coded makes it seem
> like you're unsure about the safety of the code.
>
> e.g. what could it possibly matter at this stage whether cipso_v4_cache is
> NULL or not?
>
> I think I asked this some time ago: what are the lifetime rules for this
> code as a loadable module?  What if you arbitrarily rmmod it?
>

The answer to all of your comments in this email is that these appear to be 
fragments from earlier thoughts about trying to make this code a loadable 
module.  Upon further reflection I realized that it probably doesn't make 
much sense to have this code as a module for much of the same reason that 
SELinux isn't setup as a loadable module.

As you have progressed through the patchset I'm sure you've realized by now 
this code is not intended to function as a module.  I'll clean these 
leftovers up for the next version of the patchset.

-- 
paul moore
linux security @ hp

  reply	other threads:[~2006-07-15 15:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-14 18:57 [PATCH 0/7] Latest NetLabel patch for 2.6.19 paul.moore
2006-07-14 18:57 ` [PATCH 1/7] NetLabel: documentation paul.moore
2006-07-14 18:57 ` [PATCH 2/7] NetLabel: core network changes paul.moore
2006-07-14 23:34   ` James Morris
2006-07-14 23:36     ` David Miller
2006-07-15 14:48     ` Paul Moore
2006-07-14 18:57 ` [PATCH 3/7] NetLabel: CIPSOv4 engine paul.moore
2006-07-14 23:56   ` James Morris
2006-07-15  2:03   ` James Morris
2006-07-15 14:59     ` Paul Moore
2006-07-16 16:10     ` Paul Moore
2006-07-17  1:12       ` David Miller
2006-07-17  2:42         ` Paul Moore
2006-07-17  2:53           ` David Miller
2006-07-15  2:18   ` James Morris
2006-07-15 15:03     ` Paul Moore [this message]
2006-07-15 13:08   ` James Morris
2006-07-15 13:11     ` James Morris
2006-07-15 15:13       ` Paul Moore
2006-07-15 15:09     ` Paul Moore
2006-07-15 13:15   ` James Morris
2006-07-15 15:14     ` Paul Moore
2006-07-15 22:39   ` James Morris
2006-07-15 23:26     ` Paul Moore
2006-07-14 18:57 ` [PATCH 4/7] NetLabel: core NetLabel subsystem paul.moore
2006-07-14 18:57 ` [PATCH 5/7] NetLabel: CIPSOv4 and Unlabeled packet integration paul.moore
2006-07-14 18:57 ` [PATCH 6/7] NetLabel: SELinux support paul.moore
2006-07-14 18:57 ` [PATCH 7/7] NetLabel: tie NetLabel into the Kconfig system paul.moore
  -- strict thread matches above, loose matches on Subject: below --
2006-07-17 15:52 [PATCH 0/7] Updated patchset w/James' comments paul.moore
2006-07-17 15:52 ` [PATCH 3/7] NetLabel: CIPSOv4 engine paul.moore
2006-07-28  7:56   ` David Miller

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=200607151103.49142.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=davem@davemloft.net \
    --cc=jmorris@namei.org \
    --cc=jmorris@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pratt@argus-systems.com \
    --cc=sds@epoch.ncsc.mil \
    --cc=selinux@tycho.nsa.gov \
    /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;
as well as URLs for NNTP newsgroup(s).