linux-stable.git/tools/testing/selftests/firmware, branch linux-4.1.y

tools: firmware: check for distro fallback udev cancel rule

2017-12-07T02:20:02+00:00

[ Upstream commit afb999cdef69148f366839e74470d8f5375ba5f1 ]

Some distributions (Debian, OpenSUSE) have a udev rule in place to cancel
all fallback mechanism uevents immediately. This would obviously
make it hard to test against the fallback mechanism test interface,
so we need to check for this.

Signed-off-by: Luis R. Rodriguez 
Signed-off-by: Greg Kroah-Hartman 
Signed-off-by: Sasha Levin

selftests: firmware: send expected errors to /dev/null

2017-12-07T02:20:02+00:00

[ Upstream commit 880444e214cfd293a2e8cc4bd3505f7ffa6ce33a ]

Error that we expect should not be spilled to stdout.

Without this we get:

./fw_filesystem.sh: line 58: printf: write error: Invalid argument
./fw_filesystem.sh: line 63: printf: write error: No such device
./fw_filesystem.sh: line 69: echo: write error: No such file or directory
./fw_filesystem.sh: filesystem loading works
./fw_filesystem.sh: async filesystem loading works

With it:

./fw_filesystem.sh: filesystem loading works
./fw_filesystem.sh: async filesystem loading works

Signed-off-by: Luis R. Rodriguez 
Signed-off-by: Greg Kroah-Hartman 
Signed-off-by: Sasha Levin

selftests: firmware: add empty string and async tests

2017-12-07T02:20:02+00:00

[ Upstream commit 1b1fe542b6f010cf6bc7e1c92805e1c0e133e007 ]

Now that we've added a 'trigger_async_request' knob to test the
request_firmware_nowait() API, let's use it. Also add tests for the
empty ("") string, since there have been a couple errors in that
handling already.

Since we now have real ways that the sysfs write might fail, let's add
the appropriate check on the 'echo' lines too.

Signed-off-by: Brian Norris 
Acked-by: Kees Cook 
Signed-off-by: Shuah Khan 
Signed-off-by: Sasha Levin

selftests: Introduce minimal shared logic for running tests

2015-03-13T21:13:40+00:00

This adds a Make include file which most selftests can then include to
get the run_tests logic.

On its own this has the advantage of some reduction in repetition, and
also means the pass/fail message is defined in fewer places.

However the key advantage is it will allow us to implement install very
simply in a subsequent patch.

The default implementation just executes each program in $(TEST_PROGS).

We use a variable to hold the default implementation of $(RUN_TESTS)
because that gives us a clean way to override it if necessary, ie. using
override. The mount, memory-hotplug and mqueue tests use that to provide
a different implementation.

Tests are not run via /bin/bash, so if they are scripts they must be
executable, we add a+x to several.

Signed-off-by: Michael Ellerman 
Signed-off-by: Shuah Khan

test: add firmware_class loader test

2014-07-18T01:44:19+00:00

This provides a simple interface to trigger the firmware_class loader
to test built-in, filesystem, and user helper modes. Additionally adds
tests via the new interface to the selftests tree.

Signed-off-by: Kees Cook 
Signed-off-by: Greg Kroah-Hartman