From: Eryu Guan <guan@eryu.me>
To: Christian Brauner <brauner@kernel.org>
Cc: fstests@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Christian Brauner <christian.brauner@ubuntu.com>
Subject: Re: [PATCH 0/7] idmapped mounts: extend testsuite and fixes
Date: Sun, 23 May 2021 23:08:36 +0800 [thread overview]
Message-ID: <YKpv9D1z2ox8sZte@desktop> (raw)
In-Reply-To: <20210507150100.968659-1-brauner@kernel.org>
On Fri, May 07, 2021 at 05:00:53PM +0200, Christian Brauner wrote:
> From: Christian Brauner <christian.brauner@ubuntu.com>
>
> Hey,
>
> This introduces two new idmapped mount tests.
> The first test extends the v3 fscaps tests for idmapped mounts.
> The second test verified that idmapped mounts behave correctly when
> nested user namespaces are used. In essence it creates a fairly complex
> nested user namespace hierarchy and then tests whether file ownership
> changes are correctly reflected in all idmapped mounts as seen from all
> those user namespaces.
> In addition this fixes a couple of minor things and shares more code
> between the mount-idmapped and idmapped-mounts binaries.
I applied the first 3 patches for this update. And I think patch 4 and 7
may need some rework. Patch 5 and 6 just didn't apply without patch 4.
Thanks,
Eryu
>
> Thanks!
> Christian
>
> Christian Brauner (7):
> idmapped-mounts: remove unused set_cloexec() helper
> idmapped-mounts: add missing newline to print_r()
> idmapped-mounts: split out run_test() function
> generic/637: add fscaps regression test
> idmapped-mounts: refactor helpers
> idmapped-mounts: add nested userns creation helpers
> generic/638: add nested user namespace tests
>
> .gitignore | 2 +
> src/idmapped-mounts/Makefile | 16 +-
> src/idmapped-mounts/idmapped-mounts.c | 931 ++++++++++++++++++++++++--
> src/idmapped-mounts/mount-idmapped.c | 228 +------
> src/idmapped-mounts/utils.c | 359 ++++++++--
> src/idmapped-mounts/utils.h | 102 ++-
> tests/generic/637 | 42 ++
> tests/generic/637.out | 2 +
> tests/generic/638 | 42 ++
> tests/generic/638.out | 2 +
> tests/generic/group | 2 +
> 11 files changed, 1397 insertions(+), 331 deletions(-)
> create mode 100755 tests/generic/637
> create mode 100644 tests/generic/637.out
> create mode 100755 tests/generic/638
> create mode 100644 tests/generic/638.out
>
>
> base-commit: 40818883aecd19581a71cc096d07eb9106c11b10
> --
> 2.27.0
prev parent reply other threads:[~2021-05-23 15:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 15:00 [PATCH 0/7] idmapped mounts: extend testsuite and fixes Christian Brauner
2021-05-07 15:00 ` [PATCH 1/7] idmapped-mounts: remove unused set_cloexec() helper Christian Brauner
2021-05-07 15:00 ` [PATCH 2/7] idmapped-mounts: add missing newline to print_r() Christian Brauner
2021-05-07 15:00 ` [PATCH 3/7] idmapped-mounts: split out run_test() function Christian Brauner
2021-05-07 15:00 ` [PATCH 4/7] generic/637: add fscaps regression test Christian Brauner
2021-05-23 15:07 ` Eryu Guan
2021-05-07 15:00 ` [PATCH 5/7] idmapped-mounts: refactor helpers Christian Brauner
2021-05-07 15:00 ` [PATCH 6/7] idmapped-mounts: add nested userns creation helpers Christian Brauner
2021-05-07 15:01 ` [PATCH 7/7] generic/638: add nested user namespace tests Christian Brauner
2021-05-23 15:08 ` Eryu Guan [this message]
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=YKpv9D1z2ox8sZte@desktop \
--to=guan@eryu.me \
--cc=brauner@kernel.org \
--cc=christian.brauner@ubuntu.com \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
/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