Re: [PATCH nft] tests/shell: allow running tests as non-root users

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


Thomas Haller <thaller@xxxxxxxxxx> wrote:
> Allow to opt-out from the have-real-root check via

I don't like this.  But its a step in the right direction.

To me has following issues/pain points:
 - test duration is huge (>10m with debug kernels)
 - all tests run in same netns
 - tries to unloads kernel modules after each test

The need for uid 0 wasn't big on my problem list so far because
I mostly run the tests in a VM.  But I agree its an issue for
auto-build systems / CI and the like.

> For that to be useful, we must also unshare the PID and user namespace
> and map the root user inside that namespace.

Are you sure PIDNS unshare is needed for this?

> Test that don't work without real root should check for
> [ "$NFT_TEST_HAVE_REALROOT" != 1 ] and skip gracefully.

Thats fine, see my recent RFC to add such environment
variables to check if a particular feature is supported or not.

What I don't like here is the NFT_TEST_ROOTLESS environment
variable to alter behaviour of behavior, but see below.

> -if [ "$(id -u)" != "0" ] ; then
> +if [ "$NFT_TEST_HAVE_REALROOT" = "" ] ; then
> +	# The caller can set NFT_TEST_HAVE_REALROOT to indicate us whether we
> +	# have real root. They usually don't need, and we detect it now based
> +	# on `id -u`. Note that we may unshare below, so the check inside the
> +	# new namespace won't be conclusive. We thus only detect once and export
> +	# the result.
> +	export NFT_TEST_HAVE_REALROOT="$(test "$(id -u)" = "0" && echo 1 || echo 0)"
> +fi
> +

Why not get rid of the check?  Just auto-switch to unpriv userns and
error out if that fails.  You could just print a warning/notice here and
then try userns mode.  And/or print a notice at the together with the
test summary.

> +if [ "$NFT_TEST_NO_UNSHARE" = 1 ]; then
> +	# The user opts-out from unshare. Proceed without.

Whats the use case?  If there is a good one, then i'd prefer a command
line switch rather than environment.

I think long term all of the following would be good to have:

1. run each test in its own netns
2. get rid of the forced 'nft flush ruleset' and the rmmod calls
3. Explore parallelisation of tests to reduce total test time
4. Add a SKIP return value, that tells that the test did not run
  (or some other means that allows to figure out that
   a particular test did not run because its known to not work on
   current configuration).

This would avoid false-positive 'all tests passed' when in reality
some test had to 'exit 0' because of a missing feature or lack of real

Alternatively we could just make these tests fail and leave it to the
user to figure it out, the normal expectation is for all tests to pass,
its mostly when is run on older kernel releases when it
starts acting up.

[Index of Archives]     [Netfitler Users]     [Berkeley Packet Filter]     [LARTC]     [Bugtraq]     [Yosemite Forum]

  Powered by Linux