All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guido Trentalancia <guido@trentalancia.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov
Subject: Re: [PATCH] Allowing MLS->non-MLS and vice versa upon policy reload
Date: Tue, 02 Feb 2010 18:49:55 +0100	[thread overview]
Message-ID: <1265132995.3003.41.camel@tesla.lan> (raw)
In-Reply-To: <1265132044.3114.31.camel@moss-pluto.epoch.ncsc.mil>

Hello again !

On Tue, 2010-02-02 at 12:34 -0500, Stephen Smalley wrote:
> On Tue, 2010-02-02 at 17:58 +0100, Guido Trentalancia wrote:
> > Hello again !
> > 
> > On Tue, 2010-02-02 at 11:44 -0500, Stephen Smalley wrote:
> You can't digitally sign the message w/o causing the inlined patch to be
> encoded.  So don't digitally sign patch postings.

That's fine. I won't sign patch postings anymore.

> That's ok.  checkpatch is just advisory; it still falls to a person to
> make the final judgment.

Ok.

> > Please let me know about the oops for ebitmap_destroy(). Do you think it
> > is due to the initial SID issue rather than to calling mls_destroy() for
> > a standard policy ? I wasn't saving that for a separate patch, it's just
> > that we did not discuss that further...
> 
> I'd rather track down the cause and see if we can allow
> mls_context_destroy() to be unconditionally safe.  In fact, I'm tempted
> to drop the mls_enabled tests from all of those inline functions and
> just ensure that the fields are always properly initialized and thus the
> functions will just evaluate properly even in the non-MLS case.

Well, after you told me to do that, we have context_destroy() calling
mls_context_destroy(), which in turn calls:

ebitmap_destroy(&c->range.level[i].cat);   for i={0,1}
memset(&c->range, 0, sizeof(c->range));

But in the case of a standard policy, there is no range field I suppose.

> Chris is correct btw - the kernel has no notions of "standard", or
> "MCS".  It only knows about MLS-enabled vs MLS-disabled.

Ok. So, I have now changed the message accordingly. Thanks again Chris
for pointing that out !

By the way, I think I have now got confused about the initial SID issue
that you mentioned earlier on... Could you please be more specific ? You
should know what the code looks like at the moment in ss/services.c.

Regards,

Guido



--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2010-02-02 17:50 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02 14:22 [PATCH] Allowing MLS->non-MLS and vice versa upon policy reload Guido Trentalancia
2010-02-02 16:44 ` Stephen Smalley
2010-02-02 16:58   ` Guido Trentalancia
2010-02-02 17:34     ` Stephen Smalley
2010-02-02 17:49       ` Guido Trentalancia [this message]
2010-02-02 19:01         ` Stephen Smalley
2010-02-02 18:28   ` Guido Trentalancia
2010-02-02 19:03     ` Stephen Smalley
2010-02-02 19:11       ` Stephen Smalley
  -- strict thread matches above, loose matches on Subject: below --
2010-02-04 19:27 Guido Trentalancia
2010-02-04 19:37 ` Eric Paris
2010-02-03 15:40 Guido Trentalancia
2010-02-03 15:53 ` Stephen Smalley
2010-02-03 22:07 ` James Morris
2010-02-02 16:29 Guido Trentalancia
2010-02-02 16:52 ` Christopher J. PeBenito
2010-02-01 22:36 Guido Trentalancia
2010-02-04 19:12 ` Eric Paris
2010-02-01 21:56 Guido Trentalancia
2010-02-01 21:49 Guido Trentalancia
2010-02-01 22:09 ` Stephen Smalley
2010-02-01 19:59 Guido Trentalancia
2010-02-01 20:22 ` Stephen Smalley
2010-02-01 18:25 Guido Trentalancia
2010-02-01 19:15 ` Stephen Smalley
2010-02-01 16:36 Guido Trentalancia
2010-02-01 17:41 ` Stephen Smalley
2010-01-31 22:43 Guido Trentalancia
2010-02-01 15:28 ` Stephen Smalley
2010-02-01 15:37   ` Stephen Smalley
2010-02-01 18:16 ` Stephen Smalley
2010-02-02 22:28   ` Guido Trentalancia
2010-02-03 15:48     ` Stephen Smalley

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=1265132995.3003.41.camel@tesla.lan \
    --to=guido@trentalancia.com \
    --cc=sds@tycho.nsa.gov \
    --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 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.