From: Petr Lautrbach <plautrba@redhat.com>
To: James Carter <jwcart2@gmail.com>
Cc: SElinux list <selinux@vger.kernel.org>
Subject: Re: Lets start with 3.4 userspace release
Date: Thu, 31 Mar 2022 13:41:01 +0200 [thread overview]
Message-ID: <87o81mbb8y.fsf@redhat.com> (raw)
In-Reply-To: <CAP+JOzTnOW9A7iyDeysC6pNcZA9sAqJxP1UhMYJx3-Umk6R3Ag@mail.gmail.com>
James Carter <jwcart2@gmail.com> writes:
> On Tue, Mar 29, 2022 at 3:06 PM Petr Lautrbach <plautrba@redhat.com> wrote:
>>
>> Hello,
>>
>> after 142 commits and 5 months since last SELinux userspace release,
>> it's time to think about another release.
>>
>> The current backlog of patches is bellow. Please take a look.
>>
>> This time, I'd like to release rcX every 14 days -
>> rc1 - 04-06-2022
>> rc2 - 04-20-2022
>> ...
>>
>> I'll try send patches with the release number change on Mondays before every
>> release.
>>
>>
>> Also when rc1 is out, please consider postponing non-bugfix patches
>> after the release or provide a comment that the change is not necessary
>> for this release.
>>
>>
>>
>> * https://patchwork.kernel.org/patch/12617693/ New [v2] Support static-only builds
>>
>> - v2 of https://lore.kernel.org/selinux/87lf1scgd6.fsf@alyssa.is/
>> - waits for another review
>>
>> * https://patchwork.kernel.org/patch/12639767/ New libsepol: free ebitmap on end of function
>>
> This is part of the notself patches which will not be ready for this release.
>
>> * https://patchwork.kernel.org/project/selinux/list/?series=590259 add not-self neverallow support
>>
> Still working, but not for this release.
>
>> * https://patchwork.kernel.org/patch/12672523/ New [v2] secilc: kernel policy language is infix
>>
> This one fell off my radar. I can ack and merge it.
>
>> * https://patchwork.kernel.org/project/selinux/list/?series=604679 libsepol: Adding support for not-self rules
>>
> Still working, but not for this release.
>
>> * https://patchwork.kernel.org/patch/12718352/ New [libselinux] libselinux: make threadsafe for discover_class_cache
>>
>> * https://patchwork.kernel.org/patch/12726783/ New libselinux: Prevent cached context giving wrong results
>>
>> * https://patchwork.kernel.org/project/selinux/list/?series=616731 libsepol: add sepol_av_perm_to_string |
>>
>> """
>> Since most of these functions are used in either checkpolicy or
>> audit2why (or both), it is probably fine to export these, but I would
>> appreciate any thoughts that Chris and others might have.
>> """
>>
> I need to think about this one.
>
>> * https://patchwork.kernel.org/patch/12775701/ New libsepol/cil: Write a message when a log message is truncated
>>
> I will merge this.
>
>> * https://patchwork.kernel.org/patch/12780657/ New libsepol: Use calloc when initializing bool_val_to_struct array
>>
> I will merge this.
>
>> * https://patchwork.kernel.org/patch/12783189/ New libsepol: Validate conditional expressions
>>
> I will merge this.
>
>> * https://patchwork.kernel.org/patch/12790631/ New [v3] libsemanage: Fall back to semanage_copy_dir when rename() fails
>>
> I don't know if Ondrej was planning on ack'ing it, but it seems like
> he is satisfied.
>
Thank You!
>
>>
>>
>> Petr
>>
next prev parent reply other threads:[~2022-03-31 11:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 16:56 Lets start with 3.4 userspace release Petr Lautrbach
2022-03-30 15:16 ` James Carter
2022-03-31 11:41 ` Petr Lautrbach [this message]
2022-03-31 15:15 ` Christian Göttsche
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=87o81mbb8y.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.