From: Petr Lautrbach <lautrbach@redhat.com>
To: Stephen Smalley <stephen.smalley.work@gmail.com>
Cc: James Carter <jwcart2@gmail.com>, selinux@vger.kernel.org
Subject: Re: [PATCH] libselinux: Do not inline compile_regex()
Date: Wed, 11 Jun 2025 21:17:47 +0200 [thread overview]
Message-ID: <87ikl2dr50.fsf@redhat.com> (raw)
In-Reply-To: <CAEjxPJ54dhnb40R0Zk9SDuwqXWvv2aMtD6a7MUJQzdKy1NY+sQ@mail.gmail.com>
Stephen Smalley <stephen.smalley.work@gmail.com> writes:
> On Wed, Jun 11, 2025 at 3:10 PM Petr Lautrbach <lautrbach@redhat.com> wrote:
>>
>> Stephen Smalley <stephen.smalley.work@gmail.com> writes:
>>
>> > On Wed, Jun 11, 2025 at 2:29 PM James Carter <jwcart2@gmail.com> wrote:
>> >>
>> >> Since commit bdcbbf89b9548afd452449835e58e84105a71a9a (libselinux:
>> >> limit fcontext regex path length), an error would be given if
>> >> libselinux was compiled directly. (Though, building the whole SELinux
>> >> userspace still worked.) This is because the flag "-Winline" is used
>> >> when building libselinux directly, but not when building the whole
>> >> userspace.
>> >>
>> >> Remove "inline" from the function compile_regex() in label_file.h
>> >> to allow libselinux to be built directly.
>> >>
>> >> There are four functions defined in label_file.h that are not inlined:
>> >> regex_has_meta_chars(), regex_simplify(), compile_regex(), and
>> >> insert_spec(). The first three functions are called by insert_spec()
>> >> which is called by the inlined function process_line(). This last
>> >> function is called by utils/sefcontext_compile.c which prevents
>> >> relocating the non-inlined functions to label_file.c.
>> >>
>> >> Signed-off-by: James Carter <jwcart2@gmail.com>
>> >
>> > Acked-by: Stephen Smalley <stephen.smalley.work@gmail.com>
>> >
>>
>> I'm going to postpone 3.9-rc1 to tomorrow so this change can land there.
>>
>> Ok?
>
> Or feel free to merge it now (or I can) and you can do it today,
> whichever is easiest.
I've merged it just now.
expect 3.9-rc1 in next 30 minutes
prev parent reply other threads:[~2025-06-11 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 18:28 [PATCH] libselinux: Do not inline compile_regex() James Carter
2025-06-11 18:31 ` Stephen Smalley
2025-06-11 19:10 ` Petr Lautrbach
2025-06-11 19:13 ` Stephen Smalley
2025-06-11 19:17 ` 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=87ikl2dr50.fsf@redhat.com \
--to=lautrbach@redhat.com \
--cc=jwcart2@gmail.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.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 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).