All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Ciao <qingtao.cao@windriver.com>
To: <cpebenito@tresys.com>, <slawrence@tresys.com>
Cc: <selinux@tycho.nsa.gov>
Subject: Re: [v1 PATCH 4/7] Copy and check the cond_bool_datum_t.flags during link.
Date: Mon, 29 Aug 2011 16:24:18 +0800	[thread overview]
Message-ID: <4E5B4CB2.5020104@windriver.com> (raw)
In-Reply-To: <1314604432-12156-4-git-send-email-qingtao.cao@windriver.com>

Please ignore this patch, I would re-send it with 0/7 patch for extra 
comments for the v1 patchset.

Sorry for any inconvenience!

Thanks,
Harry

On 08/29/2011 03:53 PM, Harry Ciao wrote:
> Copy the TUNABLE flag for cond_bool_datum_t during link, and check
> if there is a mismatch between boolean/tunable declaration and
> usage among modules. If this is the case, bail out with errors.
>
> Signed-off-by: Harry Ciao<qingtao.cao@windriver.com>
> ---
>   libsepol/src/link.c |   20 +++++++++++++++++---
>   1 files changed, 17 insertions(+), 3 deletions(-)
>
> diff --git a/libsepol/src/link.c b/libsepol/src/link.c
> index 421c47b..ee9675b 100644
> --- a/libsepol/src/link.c
> +++ b/libsepol/src/link.c
> @@ -587,7 +587,18 @@ static int bool_copy_callback(hashtab_key_t key, hashtab_datum_t datum,
>   		}
>   		state->base->p_bools.nprim++;
>   		base_bool = new_bool;
> -
> +		base_bool->flags = booldatum->flags;
> +	} else if ((booldatum->flags&  COND_BOOL_FLAGS_TUNABLE) !=
> +		   (base_bool->flags&  COND_BOOL_FLAGS_TUNABLE)) {
> +			/* A mismatch between boolean/tunable declaration
> +			 * and usage(for example a boolean used in the
> +			 * tunable_policy() or vice versa).
> +			 *
> +			 * This is not allowed and bail out with errors */
> +			ERR(state->handle,
> +			    "%s: Mismatch between boolean/tunable definition "
> +			    "and usage for %s", state->cur_mod_name, id);
> +			return -1;
>   	}
>
>   	/* Get the scope info for this boolean to see if this is the declaration,
> @@ -595,9 +606,12 @@ static int bool_copy_callback(hashtab_key_t key, hashtab_datum_t datum,
>   	scope = hashtab_search(state->cur->policy->p_bools_scope.table, id);
>   	if (!scope)
>   		return SEPOL_ERR;
> -	if (scope->scope == SCOPE_DECL)
> +	if (scope->scope == SCOPE_DECL) {
>   		base_bool->state = booldatum->state;
> -
> +		/* Only the declaration rather than requirement
> +		 * decides if it is a boolean or tunable. */
> +		base_bool->flags = booldatum->flags;
> +	}
>   	state->cur->map[SYM_BOOLS][booldatum->s.value - 1] = base_bool->s.value;
>   	return 0;
>

--
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:[~2011-08-29  8:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-29  7:53 [v1 PATCH 2/7] Separate tunable from boolean during compile Harry Ciao
2011-08-29  7:53 ` [v1 PATCH 3/7] Write and read TUNABLE flags in related data structures Harry Ciao
2011-08-29  8:24   ` Harry Ciao
2011-08-29  7:53 ` [v1 PATCH 4/7] Copy and check the cond_bool_datum_t.flags during link Harry Ciao
2011-08-29  8:24   ` Harry Ciao [this message]
2011-08-29  7:53 ` [PATCH 5/7] Permanently discard disabled branches of tunables in expansion Harry Ciao
2011-08-29  8:24   ` Harry Ciao
2011-08-29  7:53 ` [v1 PATCH 6/7] Skip tunable identifier and cond_node_t " Harry Ciao
2011-08-29  8:24   ` Harry Ciao
2011-08-29  7:53 ` [v1 PATCH 7/7] Create a new preserve_tunables flag in sepol_handle_t Harry Ciao
2011-08-29  8:25   ` Harry Ciao
2011-08-29  8:22 ` [v1 PATCH 2/7] Separate tunable from boolean during compile Harry Ciao
  -- strict thread matches above, loose matches on Subject: below --
2011-08-29  8:20 v1 Discard unused tunables from raw policy Harry Ciao
2011-08-29  8:21 ` [v1 PATCH 4/7] Copy and check the cond_bool_datum_t.flags during link Harry Ciao

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=4E5B4CB2.5020104@windriver.com \
    --to=qingtao.cao@windriver.com \
    --cc=cpebenito@tresys.com \
    --cc=selinux@tycho.nsa.gov \
    --cc=slawrence@tresys.com \
    /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.