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@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.
