From: Joshua Brindle <jbrindle@tresys.com>
To: Eamon Walsh <ewalsh@tycho.nsa.gov>
Cc: "Christopher J. PeBenito" <cpebenito@tresys.com>,
SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: [PATCH 1/5] libselinux: rename existing name<->value functions for compat
Date: Wed, 06 Jun 2007 18:16:34 -0400 [thread overview]
Message-ID: <46673242.1060909@tresys.com> (raw)
In-Reply-To: <46671547.5010604@tycho.nsa.gov>
Eamon Walsh wrote:
> Christopher J. PeBenito wrote:
>
> [snip]
>
>> -const char *security_class_to_string(security_class_t tclass)
>> +static const char *security_class_to_string_compat(security_class_t
>> tclass)
>> {
>> tclass = (tclass > 0 && tclass < NCLASSES) ? tclass : 0;
>> return class_to_string_data.str + class_to_string[tclass];
>> }
>>
>
> This will have to be rebased to the errno patch r2463 in trunk. Also,
> the behavior should be identical on the new functions (return EINVAL in
> the same manner).
>
> This patchset should go in prior to the mapping patchset I posted today.
>
Has anyone stacked these patches yet to see if they integrate as
expected? I assume they will since Chris' patches just change the
interfaces that you were using to obtain the kernel values.
This seems to have worked out well assuming the integration fell out
naturally :)
--
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:[~2007-06-06 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 19:10 [PATCH 1/5] libselinux: rename existing name<->value functions for compat Christopher J. PeBenito
2007-06-06 20:12 ` Eamon Walsh
2007-06-06 22:16 ` Joshua Brindle [this message]
2007-06-06 23:26 ` Eamon Walsh
-- strict thread matches above, loose matches on Subject: below --
2007-06-07 13:38 Christopher J. PeBenito
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=46673242.1060909@tresys.com \
--to=jbrindle@tresys.com \
--cc=cpebenito@tresys.com \
--cc=ewalsh@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.