From: Stephen Smalley <sds@tycho.nsa.gov>
To: Petr Lautrbach <plautrba@redhat.com>, selinux@vger.kernel.org
Subject: Re: [PATCH] libsepol: Use LIBSEPOL_3.0 and fix sepol_policydb_optimize symbol mapping
Date: Thu, 17 Oct 2019 08:41:40 -0400 [thread overview]
Message-ID: <5404baae-90bc-1dde-6994-8665a50297e5@tycho.nsa.gov> (raw)
In-Reply-To: <8cecd4d2-7b46-6d41-62fe-fd33eda2376d@tycho.nsa.gov>
On 10/15/19 10:22 AM, Stephen Smalley wrote:
> On 10/11/19 3:07 AM, Petr Lautrbach wrote:
>> There's a typo in commit b8213acff837101 ("libsepol: add a function to
>> optimize
>> kernel policy") which added new function sepol_policydb_optimize(),
>> but there's
>> sepol_optimize_policy in libsepol.map.
>>
>> LIBSEPOL_3.0 is used to follow the next release version libsepol-3.0
>>
>> Signed-off-by: Petr Lautrbach <plautrba@redhat.com>
>
> Acked-by: Stephen Smalley <sds@tycho.nsa.gov>
Thanks, applied.
>
>> ---
>> libsepol/src/libsepol.map.in | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/libsepol/src/libsepol.map.in b/libsepol/src/libsepol.map.in
>> index 6358e51f..f4946a79 100644
>> --- a/libsepol/src/libsepol.map.in
>> +++ b/libsepol/src/libsepol.map.in
>> @@ -60,7 +60,7 @@ LIBSEPOL_1.1 {
>> sepol_polcap_getname;
>> } LIBSEPOL_1.0;
>> -LIBSEPOL_1.2 {
>> +LIBSEPOL_3.0 {
>> global:
>> - sepol_optimize_policy;
>> + sepol_policydb_optimize;
>> } LIBSEPOL_1.1;
>>
>
prev parent reply other threads:[~2019-10-17 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 7:07 [PATCH] libsepol: Use LIBSEPOL_3.0 and fix sepol_policydb_optimize symbol mapping Petr Lautrbach
2019-10-11 7:10 ` Ondrej Mosnacek
2019-10-15 14:22 ` Stephen Smalley
2019-10-17 12:41 ` Stephen Smalley [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=5404baae-90bc-1dde-6994-8665a50297e5@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=plautrba@redhat.com \
--cc=selinux@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).