[PATCH] tests: Handle system-wide tunables in rseq tests

[DJ Delorie]

Michael Jeanson <mjeanson@efficios.com> writes:
> I had a quick look and I'm not quite sure how to combine the 
> 'tests-internal' and 'tests-container' targets to allow running 
> tst-rseq/tst-rseq-disable.

I seem to recall in the past, I've just added the one test to both lists
and it seemed to work.  It might depend on which two lists you're adding
it to.

> I don't know if the added complexity of the container is really required 
> given the low probability of the testsuite being run with a system-wide 
> policy on 'glibc.pthread.rseq'. Reporting the error to the user might be 
> enough.

I think a check in the test for the desired state, and UNSUPPORTED if
it's set wrong, is fine.  Especially if we're using an environment
variable to set a tunable, and the sysadmin has disallowed changing it
through a global config.  They had a reason, one hopes.