Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp477652ybd; Sat, 29 Jun 2019 00:51:00 -0700 (PDT) X-Google-Smtp-Source: APXvYqwgbWXpn+yqMO34iQU8z1Lmdv+mNVrcU86BG9P6bat1wDer5R6oU84de87ybUP0lQXT4z9t X-Received: by 2002:a17:90a:9291:: with SMTP id n17mr17766113pjo.66.1561794660531; Sat, 29 Jun 2019 00:51:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561794660; cv=none; d=google.com; s=arc-20160816; b=fgyOLczsjIjMr2B3hAMKUqolPVrDzfH/4aDTQ7KNMQZ4RytDIxgPqbvS9XTJ7IRjXV HVq7n4A/QWGFT7TkJvYtgVuWTC9NQc00NcwrSFnoR+M3oykyJsgM39kXUJ+q1D8/lY0T +Cs5eF3sPohFw1SHtnR6pj9YbArg9VOcbgC7vrapEmbbIh5Y6nGHisqZfr2e57KA7ikX RpycvAiGzqUtKFTtw6Cu3zo3yfbcJl7LWgOOE4sGWxOQOqbDmQ2IxZ/Wr/7bc2wYw576 vZs8ouxujbCvtM4MeVt+rxJvzH/8oc6d4WBO82/5362FawhjahlIX5Bq1SOQNOF3D6Rq V6XA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=6A4QPYkqZekwDN+buHLLY6SZHtB5b5SMAukbDh7QIZI=; b=gLH8ny3P1qn1+8WPbFydyfhEZORppRbJq3TeEYa/rEu8toUFev+C4uYtPg/eo8WNve r3KzzAQQphW40ZFJN8kspuSd6CXYVSGWvgo8Iz+vEOfQLt4/qjR8z1kGo0qzpQHbNxvR TjmVWxUIgO6nv1ALd8/lj0ucRPdDrVUfHNXN8R1384iWV9w5vifhoSN4U3Ktc96ZKSqY B3MhT0zNDc4FUfFokzZ/t7m0hUCgJV9VJOufHjT57e6nTd9VGhq5Ehw3Ditff3xudvsD S21OWaOc+KMY8pNFbCI8RuP4PWg0vbIzeYClxBJKPWiv7Rd7bhVPswE7ogzjxQqv+VHs 163Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m9si3955982pgq.336.2019.06.29.00.50.44; Sat, 29 Jun 2019 00:51:00 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726866AbfF2HtG (ORCPT + 99 others); Sat, 29 Jun 2019 03:49:06 -0400 Received: from mail3-relais-sop.national.inria.fr ([192.134.164.104]:42778 "EHLO mail3-relais-sop.national.inria.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726796AbfF2HtG (ORCPT ); Sat, 29 Jun 2019 03:49:06 -0400 X-IronPort-AV: E=Sophos;i="5.63,430,1557180000"; d="scan'208";a="311853501" Received: from abo-12-105-68.mrs.modulonet.fr (HELO hadrien) ([85.68.105.12]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jun 2019 09:49:04 +0200 Date: Sat, 29 Jun 2019 09:49:04 +0200 (CEST) From: Julia Lawall X-X-Sender: jll@hadrien To: Markus Elfring cc: Wen Yang , linux-kernel@vger.kernel.org, cocci@systeme.lip6.fr, Yi Wang , Gilles Muller , Nicolas Palix , Michal Marek , Masahiro Yamada Subject: Re: [v2] coccinelle: semantic code search for missing of_node_put In-Reply-To: <76641efc-2e3e-8664-03b2-4eb82f01c275@web.de> Message-ID: References: <1561690732-20694-1-git-send-email-wen.yang99@zte.com.cn> <904b9362-cd01-ffc9-600b-0c48848617a0@web.de> <76641efc-2e3e-8664-03b2-4eb82f01c275@web.de> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="8323329-766857525-1561794544=:2579" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-766857525-1561794544=:2579 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT On Sat, 29 Jun 2019, Markus Elfring wrote: > >> +if (x == NULL || ...) S > >> +... when != e = (T)x > >> + when != true x == NULL > > > > I wonder if this code exclusion specification is really required > > after a null pointer was checked before. > > I would like to add another view for this implementation detail. > > The when constraint can express a software desire which can be reasonable > to some degree. You would like to be sure that a null pointer will not occur > after a corresponding check succeeded. He wants to be sure that the true branch through a NULL pointer check is not taken. > * But I feel unsure about the circumstances under which the Coccinelle software > can determine this aspect actually. > > * I find that it can eventually make sense only after the content of > the local variable (which is identified by “x”) was modified. > Thus I would find the exclusion of assignments more useful at this place. I assume that it was added because it was found to be useful. Please actually try things out before declaring them to be useless. julia --8323329-766857525-1561794544=:2579--