From: Petr Lautrbach <plautrba@redhat.com>
To: SElinux list <selinux@vger.kernel.org>, James Carter <jwcart2@gmail.com>
Subject: Re: [PATCH] libselinux/semodule: Improve extracting message
Date: Wed, 06 Oct 2021 12:37:12 +0200 [thread overview]
Message-ID: <87o882zbfr.fsf@redhat.com> (raw)
In-Reply-To: <CAP+JOzQM1SCb+CMP-tgqsAwOna64i-Q_DOF4hprtkC20VhOz6g@mail.gmail.com>
James Carter <jwcart2@gmail.com> writes:
> On Mon, Oct 4, 2021 at 8:59 AM Petr Lautrbach <plautrba@redhat.com> wrote:
>>
>> The code doesn't check the default priority, it just looks for the
>> highest.
>>
>> Fixes:
>>
>> # semodule -E testmodule
>> Module 'testmodule' does not exist at the default priority '400'. Extracting at highest existing priority '400'.
>>
>> Signed-off-by: Petr Lautrbach <plautrba@redhat.com>
>
> Acked-by: James Carter <jwcart2@gmail.com>
Merged. Thanks!
>> ---
>> policycoreutils/semodule/semodule.c | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/policycoreutils/semodule/semodule.c b/policycoreutils/semodule/semodule.c
>> index bf9eec02a050..66ea06624eda 100644
>> --- a/policycoreutils/semodule/semodule.c
>> +++ b/policycoreutils/semodule/semodule.c
>> @@ -672,8 +672,7 @@ int main(int argc, char *argv[])
>> }
>>
>> semanage_module_info_get_priority(sh, extract_info, &curr_priority);
>> - printf("Module '%s' does not exist at the default priority '%d'. "
>> - "Extracting at highest existing priority '%d'.\n", mode_arg, priority, curr_priority);
>> + printf("Extracting at highest existing priority '%d'.\n", curr_priority);
>> priority = curr_priority;
>> }
>>
>> --
>> 2.32.0
>>
prev parent reply other threads:[~2021-10-06 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 12:57 [PATCH] libselinux/semodule: Improve extracting message Petr Lautrbach
2021-10-04 14:22 ` James Carter
2021-10-06 10:37 ` Petr Lautrbach [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=87o882zbfr.fsf@redhat.com \
--to=plautrba@redhat.com \
--cc=jwcart2@gmail.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 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.