From: Petr Vorel <petr.vorel@gmail.com>
To: Vitaly Chikunov <vt@altlinux.org>
Cc: Mimi Zohar <zohar@linux.ibm.com>,
linux-integrity@vger.kernel.org,
Gleb Fotengauer-Malinovskiy <glebfm@altlinux.org>,
"Dmitry V. Levin" <ldv@altlinux.org>
Subject: Re: [PATCH ima-evm-utils 2/2] upgrade to glibc-2.34 uses clone3 causing CI to fail
Date: Wed, 27 Oct 2021 00:07:36 +0200 [thread overview]
Message-ID: <YXh8KDsB1Q1AXwIQ@pevik> (raw)
In-Reply-To: <20211026143054.7khp5jxcyn2fzira@altlinux.org>
Hi Vitaly,
> Mimi,
> On Mon, Oct 25, 2021 at 10:49:29PM -0400, Mimi Zohar wrote:
> > Both opensuse/tumbleweed and Alt Linux have upgraded to glibc-2.34,
> > causing the CI testing to fail. Disable seccomp (which is not needed
> > anyway, since GA uses throwable virtual environments anyway).
> JFYI. We decided to update our glibc package to fall-back from clone3 to
> clone in case it's EPERM. So, after some time (perhaps a day) this
> workaround will not be needed for ALT Linux. But this will not hurts
> either and may be beneficial in the future.
I see, 09e37c71 ("__clone_internal: fallback to clone(2)/clone2(2) if clone3(2)
fails with EPERM" [1]. Interesting.
Kind regards,
Petr
[1] http://git.altlinux.org/gears/g/glibc.git?p=glibc.git;a=commitdiff;h=09e37c7111e39b7c70846aea30941c03c43e6f54
next prev parent reply other threads:[~2021-10-26 22:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 2:49 [PATCH ima-evm-utils 1/2] switch to using crun for podman Mimi Zohar
2021-10-26 2:49 ` [PATCH ima-evm-utils 2/2] upgrade to glibc-2.34 uses clone3 causing CI to fail Mimi Zohar
2021-10-26 14:30 ` Vitaly Chikunov
2021-10-26 22:07 ` Petr Vorel [this message]
2021-11-01 6:13 ` Dmitry V. Levin
2021-10-26 12:12 ` [PATCH ima-evm-utils 1/2] switch to using crun for podman Petr Vorel
2021-11-01 18:39 ` Mimi Zohar
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=YXh8KDsB1Q1AXwIQ@pevik \
--to=petr.vorel@gmail.com \
--cc=glebfm@altlinux.org \
--cc=ldv@altlinux.org \
--cc=linux-integrity@vger.kernel.org \
--cc=vt@altlinux.org \
--cc=zohar@linux.ibm.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