From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Cc: Erick Karanja <karanja99erick@gmail.com>
Subject: Re: [cocci] Searching for questionable call pairs (with SmPL)?
Date: Fri, 25 Jul 2025 09:06:28 +0200 [thread overview]
Message-ID: <cd9c1d0c-d3f2-4950-9844-ac0d1d2b58da@web.de> (raw)
In-Reply-To: <6daf83a9-abbf-45f7-b82e-c6207364fd8b@web.de>
> Will another clarification become more interesting?
Another source code search approach can eventually help to influence
some software understanding into more desirable directions.
@display@
@@
(mutex_lock
|mutex_unlock
)(
*...
);
Another test result (by the software combination “Coccinelle 1.3.0” for example):
Markus_Elfring@Sonne:…/Projekte/Linux/next-analyses> git checkout next-20250722 && /usr/bin/spatch --no-loops sound/usb/qcom/qc_audio_offload.c …/Projekte/Coccinelle/janitor/show_data_for_mutex_lock_and_unlock_calls.cocci | grep -E '^-\s+mutex_' | wc -l
…
39
* Will such information trigger further collateral evolution?
* Would lock guards become applicable at more source code places?
https://elixir.bootlin.com/linux/v6.16-rc7/source/include/linux/mutex.h#L225
Regards,
Markus
prev parent reply other threads:[~2025-07-25 7:06 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 7:45 [cocci] Searching for questionable call pairs (with SmPL)? Markus Elfring
2025-07-24 14:15 ` Markus Elfring
2025-07-24 14:47 ` Julia Lawall
2025-07-24 15:02 ` Markus Elfring
2025-07-24 15:09 ` Julia Lawall
2025-07-24 15:15 ` Markus Elfring
2025-07-24 15:25 ` Julia Lawall
2025-07-24 15:30 ` Markus Elfring
2025-07-24 16:18 ` Markus Elfring
2025-07-30 12:10 ` Markus Elfring
2025-08-01 7:33 ` Markus Elfring
2025-08-01 8:06 ` Julia Lawall
2025-08-01 8:33 ` Markus Elfring
2025-08-02 10:13 ` [cocci] Searching for lock calls without unlocking " Markus Elfring
2025-08-02 11:18 ` Markus Elfring
2025-08-02 11:28 ` Julia Lawall
2025-08-02 11:51 ` Markus Elfring
2025-08-02 11:54 ` Julia Lawall
2025-08-02 12:02 ` Markus Elfring
2025-08-02 12:10 ` Julia Lawall
2025-08-02 12:56 ` Markus Elfring
2025-08-02 13:05 ` Julia Lawall
2025-08-02 13:33 ` Markus Elfring
2025-08-02 13:45 ` Julia Lawall
2025-08-02 14:06 ` Markus Elfring
2025-08-02 15:43 ` Markus Elfring
2025-08-02 15:46 ` Julia Lawall
2025-08-02 16:01 ` Markus Elfring
2025-08-02 16:04 ` Julia Lawall
2025-08-02 16:18 ` Markus Elfring
2025-08-02 16:24 ` Julia Lawall
2025-08-02 16:35 ` Markus Elfring
2025-08-02 17:38 ` Julia Lawall
2025-08-02 18:11 ` Markus Elfring
2025-08-02 19:12 ` Julia Lawall
2025-08-02 19:26 ` Markus Elfring
2025-08-02 19:35 ` Julia Lawall
2025-08-02 19:42 ` Markus Elfring
2025-08-02 19:44 ` Julia Lawall
2025-08-02 19:48 ` [cocci] Evolution of software documentation? Markus Elfring
2025-08-03 5:24 ` [cocci] Searching for lock calls without unlocking (with SmPL)? Markus Elfring
2025-08-03 5:34 ` Julia Lawall
2025-08-03 5:55 ` Markus Elfring
2025-08-03 7:55 ` Markus Elfring
2025-08-04 10:55 ` [cocci] Searching for questionable call pairs " Markus Elfring
2025-08-04 11:25 ` [cocci] Searching for lock calls without unlocking " Markus Elfring
2025-08-06 9:30 ` [cocci] Searching for repeated actions " Markus Elfring
2025-07-24 18:37 ` [cocci] Searching for questionable call pairs " Markus Elfring
2025-07-25 7:06 ` Markus Elfring [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=cd9c1d0c-d3f2-4950-9844-ac0d1d2b58da@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=karanja99erick@gmail.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.