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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 627B1C43219 for ; Tue, 8 Nov 2022 09:40:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233726AbiKHJkw (ORCPT ); Tue, 8 Nov 2022 04:40:52 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54200 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233831AbiKHJki (ORCPT ); Tue, 8 Nov 2022 04:40:38 -0500 Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 41FDB317E9 for ; Tue, 8 Nov 2022 01:40:36 -0800 (PST) Received: by mail-lj1-x229.google.com with SMTP id t10so20297887ljj.0 for ; Tue, 08 Nov 2022 01:40:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=nwGH3xncezy8aE+xydBamp1X2UzAG0+D2pQxSdjT3Go=; b=PguF6LnLRQ/cpoVLZlxFFNefduNiIZHPgBoSTGmze3dAN+AliIFf9pQcwZzBAdrJs+ bT4oyiQjoIIApKKZOQWKdEqeMyMEW3JoLlrVuHXITZgB0NkyBzyEGfyBz/CPJBBSqZXi KNj22sWWhCl2xPc0pPLBw0D/wR1jp2xksw1JazMlcvaHQTS0eAbELD3pwm/Ob7EcxfNS O0k8jjEUg2eOCJvJgyGpDm7NVALcKS/4qOhxrLMlosDiZrSmoEtx0eIeVRXcSB7jtY8r uOCvGB64HPdapt+WCwWGecQctc1t0p+Wt8JHyRfbRFa//ys8PO6jHc5Ocsq1hrynOebU 7VQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=nwGH3xncezy8aE+xydBamp1X2UzAG0+D2pQxSdjT3Go=; b=Knqz/mkwNiNkENaoahC6gFcjfMVdgMqrUpJa7hiF+j24PY6wRAnvXXyzp6d6Aae6YU B4ubpk8NxFWwBpMjkfdlRF6y60HjYFB5iJdjUpspjU97XCyhOm35QWnuJxl+IX7OJB2T /GrTm+W2AIH0Oe8ENi2yQKdopRbkhSsOnszNUsSe05cWGBFefKf/E1uMLkpD34eGfde0 ro7uBOg8QXNbZC4biUf1m6tGZUS5cuwArojToE6kFmyeNmLNNALxZ4Ter6OfBsWLNYeS 74BZOjSAAlkttWFHXfgbENIcxg8Nn+EEAIHkjdTh1VHh1nvUMJ7Hq4zDkRTmeai7vVpQ CI6A== X-Gm-Message-State: ACrzQf2kOviKCtxrPGkIQc0QbLrt4psTWKmzoWW3chSwr2eYLJMgripa aG/Gs6ouLHAp8ovYr6P9zLm92g== X-Google-Smtp-Source: AMsMyM6g0IjhpvwW0iRhgu1Nh1ZcIdl7Lok+Zjry8sEZS7v3Grs0teipqFv3tlbCkRt6UTvGImC4Vg== X-Received: by 2002:a2e:978a:0:b0:277:107:725f with SMTP id y10-20020a2e978a000000b002770107725fmr17989655lji.417.1667900434663; Tue, 08 Nov 2022 01:40:34 -0800 (PST) Received: from [192.168.0.20] (088156142199.dynamic-2-waw-k-3-2-0.vectranet.pl. [88.156.142.199]) by smtp.gmail.com with ESMTPSA id u28-20020a2eb81c000000b0026dc7b59d8esm1658719ljo.22.2022.11.08.01.40.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 08 Nov 2022 01:40:34 -0800 (PST) Message-ID: <5791ab49-debf-53d6-f076-0e46c4f392ea@linaro.org> Date: Tue, 8 Nov 2022 10:40:33 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: Coverity: gpmc_is_valid_waitpin(): Control flow issues Content-Language: en-US To: "Niedermayr, BENEDIKT" , "rogerq@kernel.org" , "keescook@chromium.org" Cc: "gustavo@embeddedor.com" , "tony@atomide.com" , "linux-next@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-omap@vger.kernel.org" , "linux-hardening@vger.kernel.org" References: <202211041233.4D45359E7@keescook> <7cdf3d14-3f1b-7cd4-e8b9-e94b5359bf82@kernel.org> <57664014384bae015d593a7c6c6b7715fda3e89d.camel@siemens.com> From: Krzysztof Kozlowski In-Reply-To: <57664014384bae015d593a7c6c6b7715fda3e89d.camel@siemens.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/11/2022 09:15, Niedermayr, BENEDIKT wrote: >>> Another alternative with less churn is to leave them as u32 >>> but make GPMC_WAITPIN_INVALID set to a large positive number. >> Ok, I will fix that. >> Do I need to send a new fix-patch on top the current patch series? >> Or should I just send only the bugfix-patch for the coverity-bot? >> > Sorry, another Question: > Is it somehow possible to check locally if the bugfix actually fixed the bug, before I submit the patch? I think only if you have Coverity somewhere in your company set for testing kernel... Best regards, Krzysztof