From: Julia Lawall <julia.lawall@inria.fr>
To: Qing Wang <wangqing@vivo.com>
Cc: Gilles Muller <Gilles.Muller@inria.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Michal Marek <michal.lkml@markovi.net>,
cocci@systeme.lip6.fr, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] coccinelle: adjust the confidence of uninitialized_var.cocci
Date: Sun, 26 Dec 2021 11:45:16 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2112261141070.3217@hadrien> (raw)
In-Reply-To: <1639484387-76107-1-git-send-email-wangqing@vivo.com>
On Tue, 14 Dec 2021, Qing Wang wrote:
> From: Wang Qing <wangqing@vivo.com>
>
> Since uninitialized_var() was removed, this cocci should reset its
> confidence to low.
I'm not sure to understand the argument for this one. The semantic patch
in its current state is looking for declarations that hide an
uninitialized variable. The part about the uninitialized_var macro is not
there any more. The problem that is searched for seems reasonable to
address.
julia
>
> Signed-off-by: Wang Qing <wangqing@vivo.com>
> ---
> scripts/coccinelle/misc/uninitialized_var.cocci | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/coccinelle/misc/uninitialized_var.cocci b/scripts/coccinelle/misc/uninitialized_var.cocci
> index 69bbaae..79e02e3
> --- a/scripts/coccinelle/misc/uninitialized_var.cocci
> +++ b/scripts/coccinelle/misc/uninitialized_var.cocci
> @@ -18,7 +18,7 @@
> /// this kind were cleaned-up from the kernel. This cocci rule checks that
> /// the macro is not explicitly or implicitly reintroduced.
> ///
> -// Confidence: High
> +// Confidence: Low
> // Copyright: (C) 2020 Denis Efremov ISPRAS
> // Options: --no-includes --include-headers
> //
> --
> 2.7.4
>
>
prev parent reply other threads:[~2021-12-26 10:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 12:19 Qing Wang
2021-12-26 10:45 ` Julia Lawall [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.22.394.2112261141070.3217@hadrien \
--to=julia.lawall@inria.fr \
--cc=Gilles.Muller@inria.fr \
--cc=cocci@systeme.lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
--cc=wangqing@vivo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®