linux-kernel - Re: [x86/platform] d7109fe3a0: kernel-selftests.gpio.gpio-mockup.sh.fail

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 12 Sep 2021 18:10:32 +0300
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     kernel test robot <oliver.sang@...el.com>,
        Bartosz Golaszewski <bgolaszewski@...libre.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Linus Walleij <linus.walleij@...aro.org>,
        "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
        LKML <linux-kernel@...r.kernel.org>, x86@...nel.org,
        lkp@...ts.01.org, lkp@...el.com
Subject: Re: [x86/platform]  d7109fe3a0:
 kernel-selftests.gpio.gpio-mockup.sh.fail

+Cc: Bart

On Sun, Sep 12, 2021 at 11:01:58PM +0800, kernel test robot wrote:
> Greeting,
> 
> FYI, we noticed the following commit (built with gcc-9):

Thanks for the report.

First of all, please teach your bot to cut up things a bit. ~13k lines
is something not expected here, really!

> commit: d7109fe3a0991a0f7b4ac099b78c908e3b619787 ("x86/platform: Increase maximum GPIO number for X86_64")
> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git x86/urgent
> 
> 
> in testcase: kernel-selftests
> version: kernel-selftests-x86_64-d0cba0d1-1_20210907
> with following parameters:
> 
> 	group: group-01
> 	ucode: 0xe2
> 
> 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) Core(TM) i5-6500 CPU @ 3.20GHz with 32G 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@...el.com>

> 2021-09-10 00:58:57 make run_tests -C gpio
> make: Entering directory '/usr/src/perf_selftests-x86_64-rhel-8.3-kselftests-d7109fe3a0991a0f7b4ac099b78c908e3b619787/tools/testing/selftests/gpio'
> TAP version 13
> 1..1
> # selftests: gpio: gpio-mockup.sh
> # 1.  Module load tests
> # 1.1.  dynamic allocation of gpio
> # 2.  Module load error tests
> # 2.1 gpio overflow
> # test failed: unexpected chip - gpiochip0
> # GPIO gpio-mockup test FAIL
> not ok 1 selftests: gpio: gpio-mockup.sh # exit=1

Test does the overflow check with 1024 as a parameter and comments deliberately
tells about limitation. What it should do instead is to use the actual GPIO
number from the kernel configuration.

-- 
With Best Regards,
Andy Shevchenko