Re: [linux-next:master] [gpiolib] 7b61212f2a: kernel-selftests.gpio.gpio-sim.sh.fail

[Bartosz Golaszewski <brgl@bgdev.pl>]

On Sun, Dec 11, 2022 at 4:08 PM kernel test robot <oliver.sang@intel.com> wrote:
>
>
> Greeting,
>
> FYI, we noticed kernel-selftests.gpio.gpio-sim.sh.fail due to commit (built with gcc-11):
>
> commit: 7b61212f2a07a5afd213c8876e52b5c9946441e2 ("gpiolib: Get rid of ARCH_NR_GPIOS")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> [test failed on linux-next/master f925116b24c0c42dc6d5ab5111c55fd7f74e8dc7]
>
> in testcase: kernel-selftests
> version: kernel-selftests-x86_64-2ed09c3b-1_20221128
> with following parameters:
>
>         group: group-01
>
> test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
> test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
>
>
> on test machine: 4 threads Intel(R) Xeon(R) CPU E3-1225 v5 @ 3.30GHz (Skylake) with 16G memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
>
>
> If you fix the issue, kindly add following tag
> | Reported-by: kernel test robot <oliver.sang@intel.com>
> | Link: https://lore.kernel.org/oe-lkp/202212112236.756f5db9-oliver.sang@intel.com
>
>
> # selftests: gpio: gpio-sim.sh
> # trap: SIGTERM: bad trap
> # 1. chip_name and dev_name attributes
> # 1.1. Chip name is communicated to user
> # 1.2. chip_name returns 'none' if the chip is still pending
> # 1.3. Device name is communicated to user
> # 2. Creating and configuring simulated chips
> # 2.1. Default number of lines is 1
> # 2.2. Number of lines can be specified
> # 2.3. Label can be set
> # 2.4. Label can be left empty
> # 2.5. Line names can be configured
> # 2.6. Line config can remain unused if offset is greater than number of lines
> # 2.7. Line configfs directory names are sanitized
> # 2.8. Multiple chips can be created
> # 2.9. Can't modify settings when chip is live
> # 2.10. Can't create line items when chip is live
> # 2.11. Probe errors are propagated to user-space
> # Probe error was not propagated
> # GPIO gpio-sim test FAIL
> not ok 2 selftests: gpio: gpio-sim.sh # exit=1
>
>

Just sent out a fix.

Bart