From: Markus Elfring <Markus.Elfring@web.de>
To: Yuan Can <yuancan@huawei.com>, cocci@inria.fr
Cc: Julia Lawall <Julia.Lawall@inria.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
kernel-janitors@vger.kernel.org
Subject: Re: [cocci] [PATCH v3 1/2] coccinelle: locks: add missing_mutex_init.cocci script
Date: Sat, 24 Sep 2022 10:36:42 +0200 [thread overview]
Message-ID: <aa4d9a5d-aebb-d31c-d578-da03108db626@web.de> (raw)
In-Reply-To: <20220922115535.44132-2-yuancan@huawei.com>
> +@r5 depends on r4@
> +identifier r3.s;
> +struct s *mm;
> +position p;
> +@@
> +mm@p = \(kmalloc\|kzalloc\|devm_kmalloc\|devm_kzalloc\)(...)
Would you like to support another case distinction?
How do you think about to handle variable initialisations besides assignments
with a corresponding SmPL code variant?
Regards,
Markus
next prev parent reply other threads:[~2022-09-24 8:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 11:55 [cocci] [PATCH v3 0/2] coccinelle: Introduce cocci script to detect missing mutext and spin lock initialization Yuan Can
2022-09-22 11:55 ` [cocci] [PATCH v3 1/2] coccinelle: locks: add missing_mutex_init.cocci script Yuan Can
2022-09-22 18:11 ` Markus Elfring
2022-09-23 14:21 ` Julia Lawall
2022-09-23 17:02 ` [cocci] [v3 " Markus Elfring
2022-09-23 17:08 ` Julia Lawall
2022-09-23 17:47 ` Markus Elfring
2022-09-23 19:27 ` Julia Lawall
2022-09-24 8:15 ` Markus Elfring
2022-09-24 8:36 ` Markus Elfring [this message]
2022-09-24 15:40 ` [cocci] [PATCH v3 " Markus Elfring
2022-09-25 20:33 ` Markus Elfring
2022-09-22 11:55 ` [cocci] [PATCH v3 2/2] coccinelle: locks: add missing_spin_lock_init.cocci script Yuan Can
2022-09-22 17:19 ` [cocci] [PATCH v3 0/2] coccinelle: Introduce cocci script to detect missing mutext and spin lock initialization Markus Elfring
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=aa4d9a5d-aebb-d31c-d578-da03108db626@web.de \
--to=markus.elfring@web.de \
--cc=Julia.Lawall@inria.fr \
--cc=cocci@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=nicolas.palix@imag.fr \
--cc=yuancan@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.