Received: by 2002:a05:6358:5282:b0:b5:90e7:25cb with SMTP id g2csp3965561rwa; Tue, 23 Aug 2022 13:29:55 -0700 (PDT) X-Google-Smtp-Source: AA6agR4t0oC+pCGJKPzEoe1nV5Y/estitym4+u1w7ugsr2do6BEbWtUZOd8cEnTIT6S1samh3OPP X-Received: by 2002:a62:a512:0:b0:536:e2bd:e15e with SMTP id v18-20020a62a512000000b00536e2bde15emr6697365pfm.1.1661286595720; Tue, 23 Aug 2022 13:29:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1661286595; cv=none; d=google.com; s=arc-20160816; b=ZA3QIwHVq3ux76A3LfxXWdfg4hHKFvwhr4IaSftDCtX++1b/zkuQtyGCnT0P8CSjYP xW2hTyc8U3ngvYXxD5RdZGsVY9TmF2CYA85eCe0Ucs/aHf5K/Bgm6OBdFT7xTfQSvQYZ cHRpUmInKesMC9nlx49npeNVcKQ4XB0fihPLldfgpWZXaDH/0pZosd0fpZeA5QjDhGR6 3VUIclFqWveOS3aLuXhXK04Bbe7jvss34FcAZN1GL6VisCKf71hQDHJYxsQLtmhmJq/h mfZdgcSib0d69sO1VAktY8e33j+DFNSfHiFnX+yW56hN3KIwekNwyo4wA4rZnwzN/Cxr OGJg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=ytTjReeUrxoqSJ5BeQcZY9hlOg/OMaAOjybK5mQFt+A=; b=d4pucO+1WBbA5WSJijvoht80pcEZx7vKRNZVylFedNUpm1UgNkAfKPdAjUx3NB3a+N lBMgKyO57L8/A/SemvSeem7/z9bSUxR+BpHA6cWzWKEWKaHKdvC9LxrehnqGBj/SJWG9 t0+xP7QwG+xmpfAvDVajSOI+lYNryXr5tiSlyqqRIlC2yrkaNjX9DXw6FBHiNmW7U/W3 N15/zyUsZVDp7i0TsXCUvAt4a9kgeBafPROLEXDt7/Uw4mrKdVV2VDwf/UzQsyxx+YJ/ A5FIG6e6CRo5whlE1NZKe7XbWBvuXv6mMbNHOCwsPzZTIddXDwjJPY2Z3QiodR/1FGRR ZDZA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=Qy0Q9yih; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q16-20020a170902eb9000b0016b9cf35991si3007864plg.250.2022.08.23.13.29.44; Tue, 23 Aug 2022 13:29:55 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=Qy0Q9yih; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232666AbiHWTie (ORCPT + 99 others); Tue, 23 Aug 2022 15:38:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35130 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232333AbiHWTiO (ORCPT ); Tue, 23 Aug 2022 15:38:14 -0400 Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 794A6A1D14 for ; Tue, 23 Aug 2022 11:34:55 -0700 (PDT) Received: by mail-wr1-x432.google.com with SMTP id a4so18049800wrq.1 for ; Tue, 23 Aug 2022 11:34:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc; bh=ytTjReeUrxoqSJ5BeQcZY9hlOg/OMaAOjybK5mQFt+A=; b=Qy0Q9yihjuVjrN8moQnwdH5FwctVgPQjWaTW/jYlmysDVAO2t2WrbWoTwEtoaJmO7I AAM5wdq4aFShbRm62kuc1uNIEpKVeAh8SmEEQ3PfYvDK6AzvNnbwQRFbA1niDLjUyRze ADnk1oooR/czh6+WUVhvHGqF+EgkFgwl4/94d7l7cNsTJVGDee5XPIEoP+gbdxTuTEpm +ygSBBsYP68UagMawe/iKr+zmHc42vuPYH+ZHxXrIQcDzCeyYDSvwVvmYYC9SoBuVJHY MyHlPxkg1fmYUo//Epo2iJbf2qX8wqeeva53IyjehMh2NsTVCLC5JUn3hpVlqas2Ed+U iUDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc; bh=ytTjReeUrxoqSJ5BeQcZY9hlOg/OMaAOjybK5mQFt+A=; b=Oy99ssoDp8dkc/RDPS+xJuDK5Vwvp8U99rvSE7rPU+pFbr6aHLlAjcaZmBEnYWPRBk WO+CQtMNNJWhMrL5qFoRrKZTrVptb2xdFFEms4lwgvg/0Ua0HnYJKEdfMDJBKUGh9/qA w2vs9izl/Kr1kp+K6VVTn8Y13Hp4m8guEUsSV3ylrnzhgAW9JxUodkhMm4t6poowbgKp pHkz+Xn8HdzHR2I04j+8y4nOiKCRG6GdO2TkSAA2UTcSca02IC5aquIAnX784tYo4eNW yprEF7b5rtF5vNlwGeSnxQAifI5hBt3rWm+pxziWyz6Tg6epnPVvXZtB84fGSChiY9vI OfbQ== X-Gm-Message-State: ACgBeo3BdBLA94+Ck27BUGs60ed9DA4nH1VfUMn/N7qHOHM9kJJAXLOJ L6rMJt7BKc4uw/RXZFkpeBcWkg== X-Received: by 2002:a5d:50c8:0:b0:225:5a57:bd84 with SMTP id f8-20020a5d50c8000000b002255a57bd84mr6104142wrt.131.1661279694038; Tue, 23 Aug 2022 11:34:54 -0700 (PDT) Received: from myrica (cpc92880-cmbg19-2-0-cust679.5-4.cable.virginm.net. [82.27.106.168]) by smtp.gmail.com with ESMTPSA id g10-20020a05600c4eca00b003a31ca9dfb6sm27073664wmq.32.2022.08.23.11.34.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 23 Aug 2022 11:34:53 -0700 (PDT) Date: Tue, 23 Aug 2022 19:34:50 +0100 From: Jean-Philippe Brucker To: RAJESH DASARI Cc: Greg KH , stable@vger.kernel.org, linux-kernel@vger.kernel.org, ovidiu.panait@windriver.com, alexei.starovoitov@gmail.com, john.fastabend@gmail.com Subject: Re: bpf selftest failed in 5.4.210 kernel Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 23, 2022 at 10:31:40AM +0300, RAJESH DASARI wrote: > Sorry for the confusion, results are indeed confusing to me . > If I try with git bisect I get > > git bisect bad > 9d6f67365d9cdb389fbdac2bb5b00e59e345930e is the first bad commit For me bisecting points to: (A) 7c1134c7da99 ("bpf: Verifer, adjust_scalar_min_max_vals to always call update_reg_bounds()") This changes the BPF verifier output and (as expected) breaks the test_align selftest. That's why in the same series [1] another patch fixed test_align. In v5.4.y, that patch is: (B) 6a9b3f0f3bad ("selftests/bpf: Fix test_align verifier log patterns") Unfortunately commit (B) addresses multiple verifier changes, not solely (A). My guess is those changes were in series [1] and haven't been backported to v5.4. So multiple solutions: * Partially revert (B), only keeping the changes needed by (A) * Revert (A) and (B) * Add the missing commits that (B) also addresses I don't know which, I suppose it depends on the intent behind backporting (A). Ovidiu? In any case 6098562ed9df ("selftests/bpf: Fix "dubious pointer arithmetic" test") can be reverted, I can send that once we figure out the rest. Thanks, Jean [1] https://lore.kernel.org/bpf/158507130343.15666.8018068546764556975.stgit@john-Precision-5820-Tower/ > > If I try to test myself with multiple test scenarios(I have mentioned > in the previous mails) for the bad commits , I see that bad commits > are > bpf: Verifer, adjust_scalar_min_max_vals to always call update_reg_bounds() > selftests/bpf: Fix test_align verifier log patterns > selftests/bpf: Fix "dubious pointer arithmetic" test > > Thanks, > Rajesh Dasari. > > On Tue, Aug 23, 2022 at 10:04 AM Greg KH wrote: > > > > On Mon, Aug 22, 2022 at 10:23:02PM +0300, RAJESH DASARI wrote: > > > Hi, > > > > > > Please find the test scenarios which I have tried. > > > > > > Test 1: > > > > > > Running system Kernel version (tag/commit) : v5.4.210 > > > Kernel source code checkout : v5.4.210 > > > test_align test case execution status : Failure > > > > > > Test 2: > > > > > > Running system Kernel version (tag/commit) : v5.4.210 > > > Kernel source code checkout : v5.4.209 > > > test_align test case execution status : Failure > > > > > > Test 3: > > > > > > Running system Kernel version (tag/commit) : v5.4.209 > > > Kernel source code checkout : v5.4.209 > > > test_align test case execution status : Success > > > > > > Test 4: > > > > > > Running system Kernel version (tag/commit) : ACPI: APEI: Better fix to > > > avoid spamming the console with old error logs ( Kernel compiled at > > > this commit and system is booted with this change) > > > Kernel source code checkout : v5.4.210 but reverted selftests/bpf: Fix > > > test_align verifier log patterns and selftests/bpf: Fix "dubious > > > pointer arithmetic" test. If I revert only the Fix "dubious pointer > > > arithmetic" test, the testcase still fails. > > > test_align test case execution status : Success > > > > > > Test 5: > > > > > > Running system Kernel version (tag/commit) : v5.4.210 but reverted > > > commit (bpf: Verifer, adjust_scalar_min_max_vals to always call > > > update_reg_bounds() ) > > > Kernel source code checkout : v5.4.210 but reverted selftests/bpf: Fix > > > test_align verifier log patterns and selftests/bpf: Fix "dubious > > > pointer arithmetic" test. > > > test_align test case execution status : Success > > > > > > Test 6 : > > > > > > Running system Kernel version (tag/commit) : bpf: Test_verifier, #70 > > > error message updates for 32-bit right shift( Kernel compiled at this > > > commit and system is booted with this change) > > > Kernel source code checkout : v5.4.209 or v5.4.210 > > > test_align test case execution status : Failure > > > > I'm sorry, but I don't know what to do with this report at all. > > > > Is there some failure somewhere? If you use 'git bisect' do you find > > the offending commit? > > > > confused, > > > > greg k-h