From: Markus Elfring <Markus.Elfring@web.de>
To: kernel-janitors@vger.kernel.org, cocci@inria.fr,
Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: [RFC] Growing usage of the attribute “__free”?
Date: Thu, 17 Oct 2024 20:20:33 +0200 [thread overview]
Message-ID: <e8bf7b33-01da-43fb-b71e-cd86a02be2e6@web.de> (raw)
Hello,
The usage of the attribute “__free” is evolving since it became supported
for some programming interfaces by contributions of Peter Zijlstra
on 2023-05-26.
See also the commit 54da6a0924311c7cf5015533991e44fb8eb12773 ("locking:
Introduce __cleanup() based infrastructure").
I would like to present a corresponding result which can be determined
also by the means of the semantic patch language (Coccinelle)
based on source code of the software “Linux next-20241017”.
╔═══════════════════════╤═══════════╗
║ variant │ incidence ║
╠═══════════════════════╪═══════════╣
║ kfree │ 243 ║
║ device_node │ 94 ║
║ fwnode_handle │ 9 ║
║ qcom_tzmem │ 9 ║
║ gpio_device_put │ 7 ║
║ kvfree │ 7 ║
║ bitmap │ 6 ║
║ put_device │ 6 ║
║ put_cxl_root │ 5 ║
║ free_perf_xa │ 4 ║
║ pci_dev_put │ 3 ║
║ put_cxl_port │ 3 ║
║ kfree_sensitive │ 2 ║
║ snd_card_unref │ 2 ║
║ x509_free_certificate │ 2 ║
║ cleanup_dax │ 1 ║
║ del_cxl_resource │ 1 ║
║ dsmas │ 1 ║
║ firmware │ 1 ║
║ fput │ 1 ║
║ free_cmd_mem │ 1 ║
║ free_cmds │ 1 ║
║ pstore_iput │ 1 ║
║ pstore_private │ 1 ║
║ put_cxlrd │ 1 ║
╚═══════════════════════╧═══════════╝
How will development interests evolve further?
Regards,
Markus
reply other threads:[~2024-10-17 18:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e8bf7b33-01da-43fb-b71e-cd86a02be2e6@web.de \
--to=markus.elfring@web.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=cocci@inria.fr \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
/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