From: Joshua Brindle <jbrindle@tresys.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux List <SELinux@tycho.nsa.gov>
Subject: Re: [PATCH] permission value inconsistency
Date: Thu, 06 Oct 2005 12:15:27 -0400 [thread overview]
Message-ID: <43454D9F.7000109@tresys.com> (raw)
In-Reply-To: <1128528046.24059.195.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Tue, 2005-10-04 at 10:31 -0400, Joshua Brindle wrote:
>
>>These patches fix permission and common permission values being
>>incremented before they were successfully added. This may cause an
>>inconsistency in the policy in the error case.
>
>
> Isn't the error case fatal anyway?
>
Yes, the error case is fatal but there may be a possibility of an
invalid free when destroying the policydb and it certainly doesn't hurt
anything to keep the policydb consistent an an error case.
Joshua
--
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.
prev parent reply other threads:[~2005-10-06 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 14:31 [PATCH] permission value inconsistency Joshua Brindle
2005-10-05 16:00 ` Stephen Smalley
2005-10-06 16:15 ` Joshua Brindle [this message]
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=43454D9F.7000109@tresys.com \
--to=jbrindle@tresys.com \
--cc=SELinux@tycho.nsa.gov \
--cc=sds@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.