From: Julia Lawall <julia.lawall@inria.fr> To: Denis Efremov <efremov@linux.com> Cc: cocci@systeme.lip6.fr, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 0/3] Update memdup_user.cocci Date: Fri, 24 Jul 2020 22:02:07 +0200 (CEST) [thread overview] Message-ID: <alpine.DEB.2.22.394.2007242201550.2396@hadrien> (raw) In-Reply-To: <20200720162216.13248-1-efremov@linux.com> On Mon, 20 Jul 2020, Denis Efremov wrote: > Add GFP_USER to the allocation flags and handle vmemdup_user(). > > Changes in v2: > - memdup_user/vmemdup_user matching suppressed > - PoC for selfcheck virtual rule > Changes in v3: > - add missing '-' for patch rule in kmalloc/kzalloc call args > - selfcheck rule dropped from patchset > > Denis Efremov (3): > coccinelle: api: extend memdup_user transformation with GFP_USER > coccinelle: api: extend memdup_user rule with vmemdup_user() > coccinelle: api: filter out memdup_user definitions All three applied. Thanks. julia > > scripts/coccinelle/api/memdup_user.cocci | 64 ++++++++++++++++++++++-- > 1 file changed, 61 insertions(+), 3 deletions(-) > > -- > 2.26.2 > >
WARNING: multiple messages have this Message-ID (diff)
From: Julia Lawall <julia.lawall@inria.fr> To: Denis Efremov <efremov@linux.com> Cc: cocci@systeme.lip6.fr, linux-kernel@vger.kernel.org Subject: Re: [Cocci] [PATCH v3 0/3] Update memdup_user.cocci Date: Fri, 24 Jul 2020 22:02:07 +0200 (CEST) [thread overview] Message-ID: <alpine.DEB.2.22.394.2007242201550.2396@hadrien> (raw) In-Reply-To: <20200720162216.13248-1-efremov@linux.com> On Mon, 20 Jul 2020, Denis Efremov wrote: > Add GFP_USER to the allocation flags and handle vmemdup_user(). > > Changes in v2: > - memdup_user/vmemdup_user matching suppressed > - PoC for selfcheck virtual rule > Changes in v3: > - add missing '-' for patch rule in kmalloc/kzalloc call args > - selfcheck rule dropped from patchset > > Denis Efremov (3): > coccinelle: api: extend memdup_user transformation with GFP_USER > coccinelle: api: extend memdup_user rule with vmemdup_user() > coccinelle: api: filter out memdup_user definitions All three applied. Thanks. julia > > scripts/coccinelle/api/memdup_user.cocci | 64 ++++++++++++++++++++++-- > 1 file changed, 61 insertions(+), 3 deletions(-) > > -- > 2.26.2 > > _______________________________________________ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-07-24 20:02 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-20 16:22 [PATCH v3 0/3] Update memdup_user.cocci Denis Efremov 2020-07-20 16:22 ` [Cocci] " Denis Efremov 2020-07-20 16:22 ` [PATCH v3 1/3] coccinelle: api: extend memdup_user transformation with GFP_USER Denis Efremov 2020-07-20 16:22 ` [Cocci] " Denis Efremov 2020-07-20 16:22 ` [PATCH v3 2/3] coccinelle: api: extend memdup_user rule with vmemdup_user() Denis Efremov 2020-07-20 16:22 ` [Cocci] " Denis Efremov 2020-07-20 16:22 ` [PATCH v3 3/3] coccinelle: api: filter out memdup_user definitions Denis Efremov 2020-07-20 16:22 ` [Cocci] " Denis Efremov 2020-07-24 20:02 ` Julia Lawall [this message] 2020-07-24 20:02 ` [Cocci] [PATCH v3 0/3] Update memdup_user.cocci Julia Lawall 2020-07-26 16:02 Markus Elfring 2020-07-26 16:02 ` Markus Elfring
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=alpine.DEB.2.22.394.2007242201550.2396@hadrien \ --to=julia.lawall@inria.fr \ --cc=cocci@systeme.lip6.fr \ --cc=efremov@linux.com \ --cc=linux-kernel@vger.kernel.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: linkBe 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.