From: Julia Lawall <julia.lawall@inria.fr>
To: Sang-Heon Jeon <ekffu200098@gmail.com>
Cc: Nicolas Palix <nicolas.palix@imag.fr>,
cocci@inria.fr, linux-kernel@vger.kernel.org
Subject: Re: [cocci] [PATCH 3/7] coccinelle: zalloc-simple: drop the kmem_alloc rules
Date: Sun, 23 Aug 2026 21:31:28 +0200 (CEST) [thread overview]
Message-ID: <1a42788d-89a6-393d-a3aa-effee35f894@inria.fr> (raw)
In-Reply-To: <20260823161826.3805598-4-ekffu200098@gmail.com>
On Mon, 24 Aug 2026, Sang-Heon Jeon wrote:
> - kmem_alloc() was removed by commit f078d4ea8276
> ("xfs: convert kmem_alloc() to kmalloc()")
>
> - kmem_zalloc() was removed by commit 10634530f7ba
> ("xfs: convert kmem_zalloc() to kzalloc()")
>
> So drop the kmem_alloc rules.
>
> No functional change.
Applied
>
> Signed-off-by: Sang-Heon Jeon <ekffu200098@gmail.com>
> ---
> .../coccinelle/api/alloc/zalloc-simple.cocci | 41 +------------------
> 1 file changed, 1 insertion(+), 40 deletions(-)
>
> diff --git a/scripts/coccinelle/api/alloc/zalloc-simple.cocci b/scripts/coccinelle/api/alloc/zalloc-simple.cocci
> index d66c45356691..ae1d39e71e31 100644
> --- a/scripts/coccinelle/api/alloc/zalloc-simple.cocci
> +++ b/scripts/coccinelle/api/alloc/zalloc-simple.cocci
> @@ -35,7 +35,7 @@ statement S;
> @@
>
> * x = (T)\(kmalloc(E1, ...)\|vmalloc(E1)\|dma_alloc_coherent(...,E1,...)\|
> - kmalloc_node(E1, ...)\|kmem_cache_alloc(...)\|kmem_alloc(E1, ...)\|
> + kmalloc_node(E1, ...)\|kmem_cache_alloc(...)\|
> devm_kmalloc(...,E1,...)\|kvmalloc(E1, ...)\|kvmalloc_node(E1,...)\);
> if ((x==NULL) || ...) S
> * memset((T2)x,0,E1);
> @@ -88,15 +88,6 @@ statement S;
> - x = (T)kmem_cache_alloc(E3,E4);
> + x = (T)kmem_cache_zalloc(E3,E4);
> |
> -- x = kmem_alloc(E1,E2);
> -+ x = kmem_zalloc(E1,E2);
> -|
> -- x = (T *)kmem_alloc(E1,E2);
> -+ x = kmem_zalloc(E1,E2);
> -|
> -- x = (T)kmem_alloc(E1,E2);
> -+ x = (T)kmem_zalloc(E1,E2);
> -|
> - x = devm_kmalloc(E2,E1,E3);
> + x = devm_kzalloc(E2,E1,E3);
> |
> @@ -290,36 +281,6 @@ x << r4.x;
> msg="WARNING: kmem_cache_zalloc should be used for %s, instead of kmem_cache_alloc/memset" % (x)
> coccilib.report.print_report(p[0], msg)
>
> -//-----------------------------------------------------------------
> -@r5 depends on org || report@
> -type T, T2;
> -expression x;
> -expression E1,E2;
> -statement S;
> -position p;
> -@@
> -
> - x = (T)kmem_alloc@p(E1,E2);
> - if ((x==NULL) || ...) S
> - memset((T2)x,0,E1);
> -
> -@script:python depends on org@
> -p << r5.p;
> -x << r5.x;
> -@@
> -
> -msg="%s" % (x)
> -msg_safe=msg.replace("[","@(").replace("]",")")
> -coccilib.org.print_todo(p[0], msg_safe)
> -
> -@script:python depends on report@
> -p << r5.p;
> -x << r5.x;
> -@@
> -
> -msg="WARNING: kmem_zalloc should be used for %s, instead of kmem_alloc/memset" % (x)
> -coccilib.report.print_report(p[0], msg)
> -
> //-----------------------------------------------------------------
> @r6 depends on org || report@
> type T, T2;
> --
> 2.43.0
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Julia Lawall <julia.lawall@inria.fr>
To: Sang-Heon Jeon <ekffu200098@gmail.com>
Cc: Nicolas Palix <nicolas.palix@imag.fr>,
cocci@inria.fr, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/7] coccinelle: zalloc-simple: drop the kmem_alloc rules
Date: Sun, 23 Aug 2026 21:31:28 +0200 (CEST) [thread overview]
Message-ID: <1a42788d-89a6-393d-a3aa-effee35f894@inria.fr> (raw)
In-Reply-To: <20260823161826.3805598-4-ekffu200098@gmail.com>
On Mon, 24 Aug 2026, Sang-Heon Jeon wrote:
> - kmem_alloc() was removed by commit f078d4ea8276
> ("xfs: convert kmem_alloc() to kmalloc()")
>
> - kmem_zalloc() was removed by commit 10634530f7ba
> ("xfs: convert kmem_zalloc() to kzalloc()")
>
> So drop the kmem_alloc rules.
>
> No functional change.
Applied
>
> Signed-off-by: Sang-Heon Jeon <ekffu200098@gmail.com>
> ---
> .../coccinelle/api/alloc/zalloc-simple.cocci | 41 +------------------
> 1 file changed, 1 insertion(+), 40 deletions(-)
>
> diff --git a/scripts/coccinelle/api/alloc/zalloc-simple.cocci b/scripts/coccinelle/api/alloc/zalloc-simple.cocci
> index d66c45356691..ae1d39e71e31 100644
> --- a/scripts/coccinelle/api/alloc/zalloc-simple.cocci
> +++ b/scripts/coccinelle/api/alloc/zalloc-simple.cocci
> @@ -35,7 +35,7 @@ statement S;
> @@
>
> * x = (T)\(kmalloc(E1, ...)\|vmalloc(E1)\|dma_alloc_coherent(...,E1,...)\|
> - kmalloc_node(E1, ...)\|kmem_cache_alloc(...)\|kmem_alloc(E1, ...)\|
> + kmalloc_node(E1, ...)\|kmem_cache_alloc(...)\|
> devm_kmalloc(...,E1,...)\|kvmalloc(E1, ...)\|kvmalloc_node(E1,...)\);
> if ((x==NULL) || ...) S
> * memset((T2)x,0,E1);
> @@ -88,15 +88,6 @@ statement S;
> - x = (T)kmem_cache_alloc(E3,E4);
> + x = (T)kmem_cache_zalloc(E3,E4);
> |
> -- x = kmem_alloc(E1,E2);
> -+ x = kmem_zalloc(E1,E2);
> -|
> -- x = (T *)kmem_alloc(E1,E2);
> -+ x = kmem_zalloc(E1,E2);
> -|
> -- x = (T)kmem_alloc(E1,E2);
> -+ x = (T)kmem_zalloc(E1,E2);
> -|
> - x = devm_kmalloc(E2,E1,E3);
> + x = devm_kzalloc(E2,E1,E3);
> |
> @@ -290,36 +281,6 @@ x << r4.x;
> msg="WARNING: kmem_cache_zalloc should be used for %s, instead of kmem_cache_alloc/memset" % (x)
> coccilib.report.print_report(p[0], msg)
>
> -//-----------------------------------------------------------------
> -@r5 depends on org || report@
> -type T, T2;
> -expression x;
> -expression E1,E2;
> -statement S;
> -position p;
> -@@
> -
> - x = (T)kmem_alloc@p(E1,E2);
> - if ((x==NULL) || ...) S
> - memset((T2)x,0,E1);
> -
> -@script:python depends on org@
> -p << r5.p;
> -x << r5.x;
> -@@
> -
> -msg="%s" % (x)
> -msg_safe=msg.replace("[","@(").replace("]",")")
> -coccilib.org.print_todo(p[0], msg_safe)
> -
> -@script:python depends on report@
> -p << r5.p;
> -x << r5.x;
> -@@
> -
> -msg="WARNING: kmem_zalloc should be used for %s, instead of kmem_alloc/memset" % (x)
> -coccilib.report.print_report(p[0], msg)
> -
> //-----------------------------------------------------------------
> @r6 depends on org || report@
> type T, T2;
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2026-08-23 19:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 16:18 [PATCH 0/7] coccinelle: fix rules that match outdated function names Sang-Heon Jeon
2026-08-23 16:18 ` [cocci] " Sang-Heon Jeon
2026-08-23 16:18 ` [PATCH 1/7] coccinelle: remove obsolete pci_free_consistent.cocci Sang-Heon Jeon
2026-08-23 16:18 ` [cocci] " Sang-Heon Jeon
2026-08-23 17:05 ` Julia Lawall
2026-08-23 17:05 ` Julia Lawall
2026-08-23 16:18 ` [PATCH 2/7] coccinelle: alloc_cast: drop removed allocators Sang-Heon Jeon
2026-08-23 16:18 ` [cocci] " Sang-Heon Jeon
2026-08-23 19:31 ` Julia Lawall
2026-08-23 19:31 ` Julia Lawall
2026-08-23 16:18 ` [PATCH 3/7] coccinelle: zalloc-simple: drop the kmem_alloc rules Sang-Heon Jeon
2026-08-23 16:18 ` [cocci] " Sang-Heon Jeon
2026-08-23 19:31 ` Julia Lawall [this message]
2026-08-23 19:31 ` Julia Lawall
2026-08-23 16:18 ` [PATCH 4/7] coccinelle: pool_zalloc-simple: drop the pci_pool_alloc rules Sang-Heon Jeon
2026-08-23 16:18 ` [cocci] " Sang-Heon Jeon
2026-08-30 9:22 ` Julia Lawall
2026-08-23 16:18 ` [PATCH 5/7] coccinelle: kfree_mismatch: drop vmalloc_exec Sang-Heon Jeon
2026-08-23 16:18 ` [cocci] " Sang-Heon Jeon
2026-08-30 12:10 ` Julia Lawall
2026-08-23 16:18 ` [PATCH 6/7] coccinelle: atomic_as_refcounter: drop atomic_long_dec_and_lock Sang-Heon Jeon
2026-08-23 16:18 ` [cocci] " Sang-Heon Jeon
2026-08-30 12:39 ` Julia Lawall
2026-08-23 16:18 ` [PATCH 7/7] coccinelle: ifnulldev_put: update outdated helper names Sang-Heon Jeon
2026-08-23 16:18 ` [cocci] " Sang-Heon Jeon
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=1a42788d-89a6-393d-a3aa-effee35f894@inria.fr \
--to=julia.lawall@inria.fr \
--cc=cocci@inria.fr \
--cc=ekffu200098@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.