[<prev] [next>] [day] [month] [year] [list]
Message-ID: <273990e2-f289-905f-2930-725540857c67@web.de>
Date: Mon, 1 Jun 2020 08:24:39 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Denis Efremov <efremov@...ux.com>,
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>,
Coccinelle <cocci@...teme.lip6.fr>
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org,
Joe Perches <joe@...ches.com>
Subject: Re: [PATCH 2/2] Coccinelle: extend memdup_user rule with
vmemdup_user()
> +@rv depends on !patch@
> +expression from,to,size;
> +position p;
> +statement S1,S2;
> +@@
> +
> +* to = \(kvmalloc@p\|kvzalloc@p\)(size,\(GFP_KERNEL\|GFP_USER\));
> + if (to==NULL || ...) S1
> + if (copy_from_user(to, from, size) != 0)
> + S2
How does the SmPL asterisk functionality fit to the operation
modes “org” and “report”?
> +@...ipt:python depends on org && r@
I find the modification of SmPL rule dependencies also interesting.
Are these specifications really required?
Regards,
Markus
Powered by blists - more mailing lists