From: Yuan Can <yuancan@huawei.com>
To: <Julia.Lawall@inria.fr>, <nicolas.palix@imag.fr>, <cocci@inria.fr>
Cc: <yuancan@huawei.com>
Subject: [cocci] [PATCH v3 0/2] coccinelle: Introduce cocci script to detect missing mutext and spin lock initialization
Date: Thu, 22 Sep 2022 11:55:33 +0000 [thread overview]
Message-ID: <20220922115535.44132-1-yuancan@huawei.com> (raw)
This series introduce two scripts to help detect the use of mutext or spin
locks without initialization.
---
changes in v3:
- remove the redundant matching expression
- remove the redundant asterisk
changes in v2:
- adjust commit msg
- add Confidence: tag
- print out more information in the report
Yuan Can (2):
coccinelle: locks: add missing_mutex_init.cocci script
coccinelle: locks: add missing_spin_lock_init.cocci script
.../coccinelle/locks/missing_mutex_init.cocci | 76 ++++++++++++++++++
.../locks/missing_spin_lock_init.cocci | 79 +++++++++++++++++++
2 files changed, 155 insertions(+)
create mode 100644 scripts/coccinelle/locks/missing_mutex_init.cocci
create mode 100644 scripts/coccinelle/locks/missing_spin_lock_init.cocci
--
2.17.1
next reply other threads:[~2022-09-22 12:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 11:55 Yuan Can [this message]
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 ` [cocci] [PATCH v3 " Markus Elfring
2022-09-24 15:40 ` 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=20220922115535.44132-1-yuancan@huawei.com \
--to=yuancan@huawei.com \
--cc=Julia.Lawall@inria.fr \
--cc=cocci@inria.fr \
--cc=nicolas.palix@imag.fr \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).