mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: Dmitry Kalinkin <dmitry.kalinkin@gmail.com>
Cc: linux-kernel@vger.kernel.org, cocci@systeme.lip6.fr,
	Gilles Muller <Gilles.Muller@lip6.fr>,
	Nicolas Palix <nicolas.palix@imag.fr>,
	Michal Marek <mmarek@suse.cz>
Subject: Re: [PATCH] coccinelle: api: add vma_pages.cocci
Date: Sun, 17 May 2015 15:39:03 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1505171526430.2077@localhost6.localdomain6> (raw)
In-Reply-To: <1431821187-21648-1-git-send-email-dmitry.kalinkin@gmail.com>



On Sun, 17 May 2015, Dmitry Kalinkin wrote:

> This semantic patch replaces explicit computations of vma page count
> with explicit function call.

Thanks!

> Signed-off-by: Dmitry Kalinkin <dmitry.kalinkin@gmail.com>
> ---
>  scripts/coccinelle/api/vma_pages.cocci | 66 ++++++++++++++++++++++++++++++++++
>  1 file changed, 66 insertions(+)
>  create mode 100644 scripts/coccinelle/api/vma_pages.cocci
> 
> diff --git a/scripts/coccinelle/api/vma_pages.cocci b/scripts/coccinelle/api/vma_pages.cocci
> new file mode 100644
> index 0000000..2b7a748
> --- /dev/null
> +++ b/scripts/coccinelle/api/vma_pages.cocci
> @@ -0,0 +1,66 @@
> +/// Use vma_pages function on vma object instead of explicit computation.

Add an extra /// here.

> +//  Confidence: High
> +//  Keywords: vma_pages vma
> +
> +//  Based on resource_size.cocci
> +
> +virtual context
> +virtual patch
> +virtual org
> +virtual report
> +
> +//----------------------------------------------------------
> +//  For context mode
> +//----------------------------------------------------------
> +
> +@r_context depends on context && !patch && !org@

Add && !report here

> +struct vm_area_struct *vma;
> +@@
> +
> +* (vma->vm_end - vma->vm_start) >> PAGE_SHIFT
> +
> +//----------------------------------------------------------
> +//  For patch mode
> +//----------------------------------------------------------
> +
> +@r_patch1 depends on !context && patch && !org@

Add && !report here

> +struct vm_area_struct *vma;
> +@@
> +
> +- ((vma->vm_end - vma->vm_start) >> PAGE_SHIFT)
> ++ vma_pages(vma)
> +
> +@r_patch2 depends on !context && patch && !org@
> +struct vm_area_struct *vma;
> +@@
> +
> +- (vma->vm_end - vma->vm_start) >> PAGE_SHIFT
> ++ vma_pages(vma)

This rule is not needed.  An isomorphism will allow tha case with () 
around the whole thing to match the case where those parentheses are 
absent.

> +//----------------------------------------------------------
> +//  For org mode
> +//----------------------------------------------------------
> +
> +@r_org depends on !context && !patch && (org || report)@
> +struct vm_area_struct *vma;
> +position p;
> +@@
> +
> +  (vma->vm_end@p - vma->vm_start) >> PAGE_SHIFT
> +
> +@script:python depends on report@
> +p << r_org.p;
> +x << r_org.vma;
> +@@
> +
> +msg="ERROR: Missing vma_pages with %s" % (x)

I think that the message is a bit misleading.  Something like Use 
vma_pages would be better.

> +coccilib.report.print_report(p[0], msg)
> +
> +@script:python depends on org@
> +p << r_org.p;
> +x << r_org.vma;
> +@@
> +
> +msg="ERROR with %s" % (x)
> +msg_safe=msg.replace("[","@(").replace("]",")")
> +coccilib.org.print_todo(p[0], msg_safe)

The message could be the same in this case as in the previous one.

It may be good to put below the keywords:

// Comments:
// Options: --all-includes

This rule relies on type information, ie knowing whether something has 
type struct vm_area_struct *, so having more include files available may 
make that more apparent.  On the other hand, if you think the referenced 
thing will always be a local variable (as opposed to a structure field), 
then just using the current C file should be good enough, and it will be 
faster without the --all-includes option.

I tried the rule replacing struct vm_area_struct *vma; by expression vma 
and got a couple of results on other types.  One could wonder if that code 
could be improved in some way.

julia

  reply	other threads:[~2015-05-17 13:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-17  0:06 Dmitry Kalinkin
2015-05-17 13:39 ` Julia Lawall [this message]
2015-05-17 16:20   ` Dmitry Kalinkin
2015-05-17 16:23   ` [PATCHv2] " Dmitry Kalinkin
2015-05-17 20:25     ` Julia Lawall
2015-05-21  6:28       ` Michal Marek

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.02.1505171526430.2077@localhost6.localdomain6 \
    --to=julia.lawall@lip6.fr \
    --cc=Gilles.Muller@lip6.fr \
    --cc=cocci@systeme.lip6.fr \
    --cc=dmitry.kalinkin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --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 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®