From: Julia Lawall <julia.lawall@inria.fr>
To: Joe Perches <joe@perches.com>
Cc: Julia Lawall <julia.lawall@inria.fr>,
cocci <cocci@systeme.lip6.fr>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: cocci script to convert linux-kernel allocs with BITS_TO_LONGS to bitmap_alloc
Date: Wed, 14 Jul 2021 08:22:42 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2107140821140.2917@hadrien> (raw)
In-Reply-To: <42a843710a652e110b71ab6beafc3a3e6e11dfd3.camel@perches.com>
On Tue, 13 Jul 2021, Joe Perches wrote:
> On Tue, 2021-07-13 at 23:33 +0200, Julia Lawall wrote:
> > > > On Fri, 9 Jul 2021, Joe Perches wrote:
> > > > > Here is a cocci script to convert various types of bitmap allocations
> > > > > that use BITS_TO_LONGS to the more typical bitmap_alloc functions.
> >
> > I see that there is also a bitmap_free. Maybe the rule should be
> > introducing that as well?
>
> Yes, but as far as I know, it's difficult for coccinelle to convert
> the kfree() calls of any previous bitmap_alloc to bitmap_free as
> most frequently the kfree() call is in a separate function.
Often the code says a->b = foo(); and then the a->b in another function is
the same one that was the result of foo(). One could check that this is
the only assignment to a->b in the file for more confidence.
I'll add it to the rule and see how it goes.
julia
>
> Please do it if you know how, you're probably the best in the world
> at coccinelle. I don't know how...
>
> cheers, Joe
>
>
prev parent reply other threads:[~2021-07-14 6:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 20:39 Joe Perches
2021-07-10 19:50 ` Julia Lawall
2021-07-10 20:02 ` Joe Perches
2021-07-10 20:09 ` Julia Lawall
2021-07-13 21:33 ` Julia Lawall
2021-07-13 23:09 ` Joe Perches
2021-07-14 6:22 ` Julia Lawall [this message]
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.2107140821140.2917@hadrien \
--to=julia.lawall@inria.fr \
--cc=cocci@systeme.lip6.fr \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®