public inbox for
 help / color / mirror / Atom feed
From: Florian Weimer <>
To: Maxim Kuvyrkov <>
Cc: Simon Chopin <>,
	 GNU C Library <>,
	 Xi Ruoyao <>
Subject: Re: [PATCH v2] tests: gracefully handle AppArmor userns containment
Date: Wed, 14 Feb 2024 08:53:23 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Maxim Kuvyrkov's message of "Tue, 13 Feb 2024 11:36:34 +0400")

* Maxim Kuvyrkov:

> Where is EACCES coming from?  I could not find documentation
> mentioning EACCES as a possible error condition for unshare().

Presumably a seccomp filter or a Linux security module.  We don't do
that error code translation in the main library (e.g., for clone3), but
it has crept into the test suite over time.


  reply	other threads:[~2024-02-14  7:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 12:01 [PATCH] test-container: gracefully handle AppArmor containment Simon Chopin
2024-02-01 12:20 ` Xi Ruoyao
2024-02-06 11:01   ` Simon Chopin
2024-02-06 10:59 ` [PATCH v2] tests: gracefully handle AppArmor userns containment Simon Chopin
2024-02-13  7:36   ` Maxim Kuvyrkov
2024-02-14  7:53     ` Florian Weimer [this message]
2024-02-16 15:57     ` Simon Chopin

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).