From: Joshua Brindle <jbrindle@tresys.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: James Morris <jmorris@redhat.com>, selinux@tycho.nsa.gov
Subject: Re: [RFC][PATCH 0/3] Reduce number of avtab nodes
Date: Mon, 01 Aug 2005 10:58:01 -0400 [thread overview]
Message-ID: <42EE3879.2050409@tresys.com> (raw)
In-Reply-To: <1122903665.6573.281.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> <snip>
>
>- We need to be sure that we are comfortable with collapsing the type
>value space and class value space to 16 bits. That was done by the
>first patchset as part of reducing the avtab node size. The avtab_read
>code checks for value truncation when reading older binary policies; we
>should also add checks to checkpolicy to ensure that we don't overflow
>
>during policy compilation.
>
I know it won't affect the size but why not make all symbol value spaces 16 bits, just for consistency?
Also, here is a trivial patch to let audit2why compile with -Werror (which the Makefile in cvs does by default)
diff -purN nsa-patched/selinux-usr/libsepol/include/sepol/ebitmap.h nsa-new/selinux-usr/libsepol/include/sepol/ebitmap.h
--- nsa-patched/selinux-usr/libsepol/include/sepol/ebitmap.h 2005-08-01 10:53:54.503439624 -0400
+++ nsa-new/selinux-usr/libsepol/include/sepol/ebitmap.h 2005-08-01 10:51:25.564081848 -0400
@@ -46,7 +46,7 @@ static inline void ebitmap_init(ebitmap_
memset(e, 0, sizeof(*e));
}
-static inline unsigned int ebitmap_nextbit(ebitmap_t *e,
+static inline unsigned int ebitmap_nextbit(ebitmap_t *e __attribute__ ((__unused__)),
ebitmap_node_t **n,
unsigned int bit)
{
@@ -59,7 +59,7 @@ static inline unsigned int ebitmap_nextb
return (bit+1);
}
-static inline int ebitmap_node_get_bit(ebitmap_t *e,
+static inline int ebitmap_node_get_bit(ebitmap_t *e __attribute__ ((__unused__)),
ebitmap_node_t * n,
unsigned int bit)
{
--
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.
next prev parent reply other threads:[~2005-08-01 14:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 16:49 [RFC][PATCH 0/3] Reduce number of avtab nodes Stephen Smalley
2005-07-29 17:16 ` [RFC][PATCH 1/3] " Stephen Smalley
2005-07-29 17:22 ` [RFC][PATCH 2/3] " Stephen Smalley
2005-07-29 17:23 ` [RFC][PATCH 3/3] " Stephen Smalley
2005-07-29 18:01 ` [RFC][PATCH 0/3] " Stephen Smalley
2005-07-29 19:05 ` James Morris
2005-07-30 4:20 ` James Morris
2005-07-30 19:13 ` Joshua Brindle
2005-07-31 15:59 ` James Morris
2005-08-01 13:41 ` Stephen Smalley
2005-08-01 14:22 ` Luke Kenneth Casson Leighton
2005-08-01 14:58 ` Joshua Brindle [this message]
2005-08-01 15:04 ` Stephen Smalley
2005-08-01 15:09 ` Stephen Smalley
2005-08-01 15:32 ` Joshua Brindle
2005-08-04 7:57 ` Russell Coker
2005-08-04 14:35 ` Valdis.Kletnieks
2005-08-04 14:38 ` Stephen Smalley
2005-08-04 15:38 ` Joshua Brindle
2005-08-04 15:45 ` Stephen Smalley
2005-08-04 15:52 ` Joshua Brindle
2005-08-04 15:46 ` Russell Coker
2005-08-02 16:43 ` Stephen Smalley
2005-08-02 20:50 ` Stephen Smalley
2005-08-04 12:52 ` Stephen Smalley
2005-08-04 16:14 ` Stephen Smalley
2005-08-08 18:42 ` Stephen Smalley
2005-08-04 7:42 ` Russell Coker
2005-08-04 13:25 ` 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=42EE3879.2050409@tresys.com \
--to=jbrindle@tresys.com \
--cc=jmorris@redhat.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.