On Wed, Oct 20, 2021 at 8:23 AM Petr Lautrbach <plautrba@xxxxxxxxxx> wrote: > > Hello, > > 2 weeks ago I wrote that I would like to release 3.3 if there's no big > change. But in the mean time some patchsets landed on mailing list, see > bellow. My question is: do we want to wait until they are merged or it's > ok to postpone them to 3.4 development? Please let me know. > > * https://patchwork.kernel.org/project/selinux/list/?series=561273&state=* > libsepol: add fuzzer for reading binary policies > > it was reviewed by Jim who requested some changes. > I am ok with this being postponed to 3.4. Jim > * https://patchwork.kernel.org/project/selinux/list/?series=566429 > libsepol: do not pass NULL to memcpy > > v2 with requested changes, waits for review > > > * https://patchwork.kernel.org/project/selinux/patch/20211015123100.15785-1-cgzones@xxxxxxxxxxxxxx/ > libselinux: use dummy variable to silence glibc 2.34 warnings > > reviewed by Nicolas, work in progress I guess > > > * https://patchwork.kernel.org/project/selinux/list/?series=566423&state=* > Parallel setfiles/restorecon > > 3rd version of the patchset, waits for review > > > > Petr >
