From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.groups.io (mail02.groups.io [66.175.222.108]) by spool.mail.gandi.net (Postfix) with ESMTPS id 7CDCAD8108C for ; Mon, 13 Nov 2023 11:24:09 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=TiUyR279NciU7WcB7u6rcLqeu1ER1EzqJg2DHrDwCBI=; c=relaxed/simple; d=groups.io; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From:In-Reply-To:Precedence:List-Subscribe:List-Help:Sender:List-Id:Mailing-List:Delivered-To:Reply-To:List-Unsubscribe-Post:List-Unsubscribe:Content-Language:Content-Type:Content-Transfer-Encoding; s=20140610; t=1699874648; v=1; b=O8sJwDHzmVluudVjaeYEudPJVewS0WR0AdHFbjf/ko/t2p2KCW3Agm9bAKyIAmKmELBVQ4oa ABctsjVoFxJSnM9/P+nhHX96Ec2IWGTfDXXvi8U5KKE5a4qhRQ+oul3p57hHUwBj2WhmiexS//V t9fxSvK57Yb6mkeJ/zkkz+20= X-Received: by 127.0.0.2 with SMTP id OSlmYY7687511x6xuiLWjEwP; Mon, 13 Nov 2023 03:24:08 -0800 X-Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mx.groups.io with SMTP id smtpd.web10.34671.1699874647206306573 for ; Mon, 13 Nov 2023 03:24:07 -0800 X-Received: from mimecast-mx02.redhat.com (mx-ext.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-345-wqW4t5GtNveY4HugLv1I_w-1; Mon, 13 Nov 2023 06:24:03 -0500 X-MC-Unique: wqW4t5GtNveY4HugLv1I_w-1 X-Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id E0E843C100A6; Mon, 13 Nov 2023 11:24:02 +0000 (UTC) X-Received: from [10.39.192.220] (unknown [10.39.192.220]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C8B60492BE0; Mon, 13 Nov 2023 11:24:01 +0000 (UTC) Message-ID: Date: Mon, 13 Nov 2023 12:24:00 +0100 MIME-Version: 1.0 Subject: Re: [edk2-devel] [PATCH v2 2/5] MdeModulePkg/Bus/Pci/PciBusDxe: Fix MISSING_BREAK Coverity issues To: Ranbir Singh , "Kinney, Michael D" Cc: "devel@edk2.groups.io" , "Ni, Ray" , Veeresh Sangolli References: <20231107061959.113213-1-rsingh@ventanamicro.com> <20231107061959.113213-3-rsingh@ventanamicro.com> <88d1e976-505d-699e-013b-43891a94eb2b@redhat.com> From: "Laszlo Ersek" In-Reply-To: X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.9 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Precedence: Bulk List-Subscribe: List-Help: Sender: devel@edk2.groups.io List-Id: Mailing-List: list devel@edk2.groups.io; contact devel+owner@edk2.groups.io Reply-To: devel@edk2.groups.io,lersek@redhat.com List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: X-Gm-Message-State: lZ2rnv4IfwRIVE6PykRL3Gsjx7686176AA= Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-GND-Status: LEGIT Authentication-Results: spool.mail.gandi.net; dkim=pass header.d=groups.io header.s=20140610 header.b=O8sJwDHz; spf=pass (spool.mail.gandi.net: domain of bounce@groups.io designates 66.175.222.108 as permitted sender) smtp.mailfrom=bounce@groups.io; dmarc=fail reason="SPF not aligned (relaxed), DKIM not aligned (relaxed)" header.from=redhat.com (policy=none) On 11/8/23 05:29, Ranbir Singh wrote: > Hi Mike, > > I agree that any manual inspection is sort of a burden, more so when it > becomes repetitive in the long run. > > When I was doing these Coverity checks (Nov-Dec' 2022), I was working in > Dell and had access to the real systems to check the execution flow as > well as the Coverity status. I could never post these patches while > being there, but happened to raise Bugzilla's and post them there > instead hoping that they would be taken up by somebody further. > > I am no longer with Dell and later on when I found that those BZ / > issues pointed out by Coverity still exist as there are no code changes > in related contexts, I thought of taking them forward in whatever > limited capacity I can. I am a bit hesitant to do any further code > changes as now I do not have any systems to check the execution flow as > well as the Coverity status. So, I do not guarantee, but will try to > make the code changes wherever it is easy to ascertain that the > functional flow would not be impacted and the same issue won't exist > anymore. This makes me a bit sad. I was happy to see that a company seriously invested in cleaning up Coverity issue reports all over edk2. If you don't have the environment and/or the assignment to continue doing that, then I agree that further tweaking these patches is unjustifed. (Sorry, I didn't realize the background when I reviewed your patches.) New versions would effectively mean "untested" code (untested as in not tested with Coverity specifically). In particular because the purported warning fixes will require real edk2 review (and occasionally regression testing even), which doesn't look good if we can't even be sure that the change actually placates coverity. I guess we should upstream those of your patches that are fine right as they are, and drop the rest for now. (A pity!) Accordingly, if you think some of my review comments are not especially important in this light (i.e., whenever it is better to take the patch as is, than to drop an updated version due to untestability), then please do comment so explicitly! Laszlo -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#111142): https://edk2.groups.io/g/devel/message/111142 Mute This Topic: https://groups.io/mt/102438299/7686176 Group Owner: devel+owner@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io] -=-=-=-=-=-=-=-=-=-=-=-