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
