[<prev] [next>] [day] [month] [year] [list]
Message-ID: <d1034b7b-12f9-a4c7-868e-1579668eb73e@web.de>
Date: Mon, 8 Jun 2020 21:07:24 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Denis Efremov <efremov@...ux.com>,
Coccinelle <cocci@...teme.lip6.fr>,
Gilles Muller <Gilles.Muller@...6.fr>,
Julia Lawall <Julia.Lawall@...6.fr>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Michal Marek <michal.lkml@...kovi.net>,
Nicolas Palix <nicolas.palix@...g.fr>
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org,
Thierry Martinez <Thierry.Martinez@...ia.fr>
Subject: Re: [PATCH v2 4/4] coccinelle: api: add selfcheck for memdup_user
rule
> Check that the rule matches vmemdup_user implementation.
> memdup_user is out of scope because we are not matching
> kmalloc_track_caller() function.
I find this change description improvable.
Will it become helpful (for example) to mention that you would like to
add another operation mode?
> +@...alize:python depends on selfcheck@
> +filtered << merge.filtered;
> +checked_files << merge.checked_files;
> +@@
Are we looking for better software documentation for such functionality?
Regards,
Markus
Powered by blists - more mailing lists