From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2 00/14] Improved tool for testing across multiple namespaces
Date: Sat, 8 Apr 2023 01:12:56 +0200 [thread overview]
Message-ID: <20230408011256.455ec451@elisabeth> (raw)
In-Reply-To: <20230406032819.707441-1-david@gibson.dropbear.id.au>
On Thu, 6 Apr 2023 13:28:05 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> This series extends the "nsholder" tool we use in the tests to
> "nstool" with some more features. In particular it allows entering an
> established namespace with capabilities intact, and it allows entering
> them with less verbose options than nsenter.
>
> For now this only gives a modest simplification of the tests, but it
> should enable more in future.
>
> I haven't managed to get all the way through the testsuite with this:
> it's wedging in the IPv4 UDP throughput tests, but that's happening
> for me with the main branch too. I'll debug that, but I don't want to
> delay this series on that for now.
>
> Changes since v1:
> * Fixed a bunch of bad indentation from a bad copy/paste
> * Assorted minor cleanups based on review from Stefano
>
> David Gibson (14):
> nstool: Rename nsholder to nstool
> nstool: Reverse parameters to nstool
> nstool: Move description of its operation modes from comment to usage
> nstool: Split some command line parsing and socket setup to
> subcommands
> nstool: Replace "pid" subcommand with "info" subcommand
> nstool: Detect what namespaces target is in
> nstool: Add magic number to advertized information
> nstool: Helpers to iterate through namespace types
> nstool: Add nstool exec command to execute commands in an nstool
> namespace
> nstool: Add --keep-caps option to nstool exec
> test: Initialise ${TRACE} properly
> test: Use "nstool exec" to slightly simplify tests
> nstool: Advertise the holder's cwd (in its mountns) across the socket
> nstool: Enter holder's cwd when changing mount ns with nstool exec
Pushed, thanks.
--
Stefano
prev parent reply other threads:[~2023-04-07 23:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 3:28 [PATCH v2 00/14] Improved tool for testing across multiple namespaces David Gibson
2023-04-06 3:28 ` [PATCH v2 01/14] nstool: Rename nsholder to nstool David Gibson
2023-04-06 3:28 ` [PATCH v2 02/14] nstool: Reverse parameters " David Gibson
2023-04-06 3:28 ` [PATCH v2 03/14] nstool: Move description of its operation modes from comment to usage David Gibson
2023-04-06 3:28 ` [PATCH v2 04/14] nstool: Split some command line parsing and socket setup to subcommands David Gibson
2023-04-06 3:28 ` [PATCH v2 05/14] nstool: Replace "pid" subcommand with "info" subcommand David Gibson
2023-04-06 3:28 ` [PATCH v2 06/14] nstool: Detect what namespaces target is in David Gibson
2023-04-06 3:28 ` [PATCH v2 07/14] nstool: Add magic number to advertized information David Gibson
2023-04-06 3:28 ` [PATCH v2 08/14] nstool: Helpers to iterate through namespace types David Gibson
2023-04-06 3:28 ` [PATCH v2 09/14] nstool: Add nstool exec command to execute commands in an nstool namespace David Gibson
2023-04-06 3:28 ` [PATCH v2 10/14] nstool: Add --keep-caps option to nstool exec David Gibson
2023-04-06 3:28 ` [PATCH v2 11/14] test: Initialise ${TRACE} properly David Gibson
2023-04-06 3:28 ` [PATCH v2 12/14] test: Use "nstool exec" to slightly simplify tests David Gibson
2023-04-06 3:28 ` [PATCH v2 13/14] nstool: Advertise the holder's cwd (in its mountns) across the socket David Gibson
2023-04-06 3:28 ` [PATCH v2 14/14] nstool: Enter holder's cwd when changing mount ns with nstool exec David Gibson
2023-04-07 23:12 ` Stefano Brivio [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=20230408011256.455ec451@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).