[PATCH v8 0/8] Add support for memory sealing
Jeff Xu
jeffxu@google.com
Tue Feb 11 17:25:27 GMT 2025
On Tue, Feb 11, 2025 at 12:19 AM Florian Weimer <fweimer@redhat.com> wrote:
>
> * Cristian Rodríguez:
>
> > On Mon, Feb 3, 2025 at 4:40 PM Florian Weimer <fweimer@redhat.com> wrote:
> >>
> >> * Adhemerval Zanella Netto:
> >>
> >> >> CRIU needs to be able to unmap everything that was initially loaded by
> >> >> the kernel and glibc. This will stop working if we use mseal for glibc
> >> >> itself.
> >> >
> >> > So in this case the easiest way it to filter of mseal (with seccomp or
> >> > something related) and disable sealing. I don't have a easy solution.
> >>
> >> Please test with CRIU and trace and find a way to make them work again
> >> if they are broken.
> >
> > that is a kernel problem afaik.. .why libc has to care about this limitation ?
>
> We want CRIU and similar tools to be able to build with glibc 2.42 and
> later, without distributions having to provide two separate glibc
> versions.
>
Statically linking with glibc can be a walk around solution.
Thanks
-Jeff
> Thanks,
> Florian
>
More information about the Libc-alpha
mailing list