From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7DE56C433F5 for ; Sun, 12 Sep 2021 15:10:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 539D86108E for ; Sun, 12 Sep 2021 15:10:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235361AbhILPLx (ORCPT ); Sun, 12 Sep 2021 11:11:53 -0400 Received: from mga03.intel.com ([134.134.136.65]:8716 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229653AbhILPLw (ORCPT ); Sun, 12 Sep 2021 11:11:52 -0400 X-IronPort-AV: E=McAfee;i="6200,9189,10105"; a="221515784" X-IronPort-AV: E=Sophos;i="5.85,287,1624345200"; d="scan'208";a="221515784" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Sep 2021 08:10:38 -0700 X-IronPort-AV: E=Sophos;i="5.85,287,1624345200"; d="scan'208";a="698291568" Received: from smile.fi.intel.com (HELO smile) ([10.237.68.40]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Sep 2021 08:10:35 -0700 Received: from andy by smile with local (Exim 4.95-RC2) (envelope-from ) id 1mPR7o-002xJD-R6; Sun, 12 Sep 2021 18:10:32 +0300 Date: Sun, 12 Sep 2021 18:10:32 +0300 From: Andy Shevchenko To: kernel test robot , Bartosz Golaszewski Cc: Thomas Gleixner , Linus Walleij , "Rafael J. Wysocki" , LKML , x86@kernel.org, lkp@lists.01.org, lkp@intel.com Subject: Re: [x86/platform] d7109fe3a0: kernel-selftests.gpio.gpio-mockup.sh.fail Message-ID: References: <20210912150158.GF25450@xsang-OptiPlex-9020> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210912150158.GF25450@xsang-OptiPlex-9020> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org +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 > 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