[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240429.Chahf2sai1au@digikod.net>
Date: Mon, 29 Apr 2024 14:39:08 +0200
From: Mickaël Salaün <mic@...ikod.net>
To: Kees Cook <keescook@...omium.org>
Cc: Christian Brauner <brauner@...nel.org>,
Jakub Kicinski <kuba@...nel.org>, Mark Brown <broonie@...nel.org>,
Shengyu Li <shengyu.li.evgeny@...il.com>, Shuah Khan <shuah@...nel.org>,
"David S . Miller" <davem@...emloft.net>, Günther Noack <gnoack@...gle.com>,
Will Drewry <wad@...omium.org>, kernel test robot <oliver.sang@...el.com>,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH v1 2/5] selftests/landlock: Fix FS tests when run on a
private mount point
On Fri, Apr 26, 2024 at 12:38:17PM -0700, Kees Cook wrote:
> On Fri, Apr 26, 2024 at 07:22:49PM +0200, Mickaël Salaün wrote:
> > According to the test environment, the mount point of the test's working
> > directory may be shared or not, which changes the visibility of the
> > nested "tmp" mount point for the test's parent process calling
> > umount("tmp").
> >
> > This was spotted while running tests on different Linux distributions,
> > with different mount point configurations.
>
> Which distros did what?
Actually it's not related to distros, but rather container runtime
(Docker) vs. non-container environment. With Docker (at least on my
environment) all mount points are private, which is not the case (by
default) when running the same UML environment not in a container. See
https://github.com/landlock-lsm/landlock-test-tools/pull/4
I'll update the description.
Powered by blists - more mailing lists