From: KaiGai Kohei <kaigai@ak.jp.nec.com>
To: James Morris <jmorris@namei.org>
Cc: selinux@tycho.nsa.gov, linux-security-module@vger.kernel.org,
Stephen Smalley <sds@tycho.nsa.gov>,
KaiGai Kohei <kaigai@kaigai.gr.jp>
Subject: Re: [PATCH][RFC] selinux: fix a couple of sparse warnings
Date: Tue, 09 Feb 2010 16:09:18 +0900 [thread overview]
Message-ID: <4B710A1E.10205@ak.jp.nec.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1002081013130.25332@tundra.namei.org>
(2010/02/08 8:14), James Morris wrote:
> Please review.
>
> These warnings were introduced in commit
> 44c2d9bdd7022ca7d240d5adc009296fc1c6ce08
Please wait for a few days more.
It might be the right answer to revert this commit, not fixing
compiler warning.
http://marc.info/?l=selinux&m=126569829629708&w=2
> ----
>
>
> selinux: fix a couple of sparse warnings
>
> Fix a couple of sparse warnings for callers of
> context_struct_to_string, which takes a *u32, not an *int.
>
> These cases are harmless as the values are not used.
>
> Signed-off-by: James Morris<jmorris@namei.org>
>
> diff --git a/security/selinux/ss/services.c b/security/selinux/ss/services.c
> index 4e976f5..0e5c3a4 100644
> --- a/security/selinux/ss/services.c
> +++ b/security/selinux/ss/services.c
> @@ -455,7 +455,8 @@ static void security_dump_masked_av(struct context *scontext,
> char *scontext_name = NULL;
> char *tcontext_name = NULL;
> char *permission_names[32];
> - int index, length;
> + int index;
> + u32 length;
> bool need_comma = false;
>
> if (!permissions)
> @@ -807,7 +808,7 @@ int security_bounded_transition(u32 old_sid, u32 new_sid)
> if (rc) {
> char *old_name = NULL;
> char *new_name = NULL;
> - int length;
> + u32 length;
>
> if (!context_struct_to_string(old_context,
> &old_name,&length)&&
>
>
>
--
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai@ak.jp.nec.com>
--
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:[~2010-02-09 7:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-07 23:14 [PATCH][RFC] selinux: fix a couple of sparse warnings James Morris
2010-02-09 7:09 ` KaiGai Kohei [this message]
2010-02-16 1:46 ` KaiGai Kohei
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=4B710A1E.10205@ak.jp.nec.com \
--to=kaigai@ak.jp.nec.com \
--cc=jmorris@namei.org \
--cc=kaigai@kaigai.gr.jp \
--cc=linux-security-module@vger.kernel.org \
--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.