Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp5489186pxb; Wed, 26 Jan 2022 13:14:40 -0800 (PST) X-Google-Smtp-Source: ABdhPJyaW79sraTkDoMKZ5d2Wmt/GOrSh2ntSbM2c2iUwZpO6g4H0+hIHNr64BUnVtJ5/cFwcAXT X-Received: by 2002:a17:906:c146:: with SMTP id dp6mr469013ejc.1.1643231680755; Wed, 26 Jan 2022 13:14:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643231680; cv=none; d=google.com; s=arc-20160816; b=Mj1mUvLVM5yQ6A5Z8vI+2kEJe9+TYR2S1r5zjcp0rnaOiNPcJp7w5GtTX3miMFd9Jq hk/T6Ww4FgaZPeuWIWd/62Dlbzw514f/N8LpwqdU828yQxDwmbfVq/Pj5AlnrWB4Sp8i FKWcN9Efir3aP+jgpT7Y7NkFvhQTJSUCoZtOcEwMrHeY4gQWcGcYFdBj2dSPcti+hqz6 la+mn+vV78X3Jo63te7kanLNvcx2FKOEFvRn+WtZnDfY4KfdJiQZ5RCXHSm3j4Erip8y n4JllE0ewKWJV3rHBrAtlwg7dHyrYNmZKMvI6ENcEJ0RgPMBkrzSfUS7XIkqG/Vpi3Cp y+Ag== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=MYbWGhb2dI7qqmnwKRQSCaKWF3hEeCXy0lt86QilvSE=; b=epoGOgZkd0H5wesdWRdlRsmA4s9Tc1CphlXjQbdqFhXLuzECFIRW3oZ5zhC8Mwj8nX 3O7K/6QyQriqqAt+HgQ3HQZSXxO6pLyAWvk88nLawBSdulfhe6ruVo8alImcaN7CqW1+ BNYVSGYa2MeReInP1AOJ62vWBk1ecRmxrxXZ4uHt6dAGJYmA/pvjFXNoZmG1t9deG61q VeXhyOratX+bogi8wpBvD/viJ2QG0cN5hphteBV4TJHQv8eR7RofLeBqN24m++gE57vx OSpFoPQD7YGTMscNtYBC2Id8OMZeHfr2HF2HorL5IK64R8F1LLB4/9mPIpEzE/onsoKj FxUw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id b11si209851edz.444.2022.01.26.13.14.13; Wed, 26 Jan 2022 13:14:40 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241355AbiAZMe1 (ORCPT + 99 others); Wed, 26 Jan 2022 07:34:27 -0500 Received: from foss.arm.com ([217.140.110.172]:36820 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241330AbiAZMe0 (ORCPT ); Wed, 26 Jan 2022 07:34:26 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 008D8D6E; Wed, 26 Jan 2022 04:34:26 -0800 (PST) Received: from e120937-lin (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 41B1A3F793; Wed, 26 Jan 2022 04:34:25 -0800 (PST) Date: Wed, 26 Jan 2022 12:34:18 +0000 From: Cristian Marussi To: Vincenzo Frascino Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org, shuah@kernel.org Subject: Re: [PATCH 2/5] kselftest: Fix vdso_test_time to pass on skips Message-ID: <20220126123418.GH6113@e120937-lin> References: <20220126102723.23300-1-cristian.marussi@arm.com> <20220126102723.23300-3-cristian.marussi@arm.com> <8d513be7-a99d-2b7f-6767-a378742ef3fa@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8d513be7-a99d-2b7f-6767-a378742ef3fa@arm.com> User-Agent: Mutt/1.9.4 (2018-02-28) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 26, 2022 at 12:22:45PM +0000, Vincenzo Frascino wrote: > Hi Cristian, > Hi Vincenzo, thanks for the feedback. > On 1/26/22 10:27 AM, Cristian Marussi wrote: > > When a vDSO symbol is not found, all the testcases in vdso_test_abi usually > > report a SKIP, which, in turn, is reported back to Kselftest as a PASS. > > > > Testcase vdso_test_time, instead, reporting a SKIP, causes the whole set of > > tests within vdso_test_abi to be considered FAIL when symbol is not found. > > > > Fix it reporting a PASS when vdso_test_time cannot find the vdso symbol. > > > > Cc: Vincenzo Frascino > > Signed-off-by: Cristian Marussi > > --- > > Seen as a failure on both a JUNO and a Dragonboard on both recent and old > > kernels/testruns: > > > > root@deb-buster-arm64:~# /opt/ksft/vDSO/vdso_test_abi > > [vDSO kselftest] VDSO_VERSION: LINUX_2.6.39 > > The time is 1637922136.675304 > > The time is 1637922136.675361000 > > The resolution is 0 1 > > clock_id: CLOCK_REALTIME [PASS] > > The time is 1927.760604900 > > The resolution is 0 1 > > clock_id: CLOCK_BOOTTIME [PASS] > > The time is 1637922136.675649700 > > The resolution is 0 1 > > clock_id: CLOCK_TAI [PASS] > > The time is 1637922136.672000000 > > The resolution is 0 4000000 > > clock_id: CLOCK_REALTIME_COARSE [PASS] > > The time is 1927.761005600 > > The resolution is 0 1 > > clock_id: CLOCK_MONOTONIC [PASS] > > The time is 1927.761132780 > > The resolution is 0 1 > > clock_id: CLOCK_MONOTONIC_RAW [PASS] > > The time is 1927.757093740 > > The resolution is 0 4000000 > > clock_id: CLOCK_MONOTONIC_COARSE [PASS] > > Could not find __kernel_time <<< This caused a FAIL as a whole > > root@deb-buster-arm64:~# echo $? > > 1 > > > > e.g.: https://lkft.validation.linaro.org/scheduler/job/2192570#L27778 > > --- > > tools/testing/selftests/vDSO/vdso_test_abi.c | 3 ++- > > 1 file changed, 2 insertions(+), 1 deletion(-) > > > > diff --git a/tools/testing/selftests/vDSO/vdso_test_abi.c b/tools/testing/selftests/vDSO/vdso_test_abi.c > > index 3d603f1394af..7dcc66d1cecf 100644 > > --- a/tools/testing/selftests/vDSO/vdso_test_abi.c > > +++ b/tools/testing/selftests/vDSO/vdso_test_abi.c > > @@ -90,8 +90,9 @@ static int vdso_test_time(void) > > (vdso_time_t)vdso_sym(version, name[2]); > > > > if (!vdso_time) { > > + /* Skip if symbol not found: consider skipped tests as passed */ > > printf("Could not find %s\n", name[2]); > > - return KSFT_SKIP; > > + return KSFT_PASS; > > My preference would be to keep "KSFT_SKIP" here and verify separately the return > status of each test. This would maintain compliance with the kselftest API. > Could you please test the patch in-reply-to this one (will be sent shortly) and > let me know if it works for you? > Sure, I was indeed not sure my solution was what you wanted. > If it does feel free to fold it in the next version of your series with your > "Tested-by:" otherwise let me know. Sure, I'll do and keep you on CC. Thanks, Cristian