From: Julia Lawall <julia.lawall@inria.fr>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: cocci@inria.fr
Subject: Re: [cocci] Need some help with spatch
Date: Fri, 5 Nov 2021 22:59:52 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2111052256000.3000@hadrien> (raw)
In-Reply-To: <17a7a40f-b736-e0ea-02ae-1b03ef4483bf@suse.cz>
> for example the cocci patch is supposed to change all "page" to "slab", but
> some lines are patched like this:
>
> - __free_slab(page->slab_cache, page);
> + __free_slab(page->slab_cache, slab);
In the original definition of rcu_free_slab, the second argument has the
form page_slab(page). This triggers the first disjunct of:
(
- page_slab(page)
+ slab
|
- compound_order(page)
+ slab_order(slab)
|
- PageSlab(page)
+ PageSlab(slab_page(slab))
|
- page_address(page)
+ slab_address(slab)
|
- page_size(page)
+ slab_size(slab)
|
- page_to_nid(page)
+ slab_nid(slab)
|
- page->pages
+ slab->slabs
|
- page
+ slab
)
Once a disjuntc has been chosen for a particular statement, then the
remaining ones are not taken into account. So -page + slab is not taken
into account.
I wonder if you could just have one rule to change all occurences of page
to slab, and then have individual rules to change eg page_address(slab) to
slab_address(slab). Then all the cases should be taken into account.
julia
next prev parent reply other threads:[~2021-11-05 22:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 16:12 [cocci] Need some help with spatch Vlastimil Babka
2021-11-05 16:20 ` Luis Chamberlain
2021-11-06 6:44 ` Julia Lawall
2021-11-07 23:08 ` Vlastimil Babka
2021-11-08 14:35 ` Vlastimil Babka
2021-11-08 14:45 ` Julia Lawall
2021-11-08 16:53 ` Vlastimil Babka
2021-11-08 17:01 ` Julia Lawall
2021-11-05 20:56 ` Julia Lawall
2021-11-05 21:13 ` Julia Lawall
2021-11-05 21:24 ` Vlastimil Babka
2021-11-05 21:27 ` Julia Lawall
2021-11-05 21:31 ` Julia Lawall
2021-11-05 21:32 ` Vlastimil Babka
2021-11-05 21:43 ` Julia Lawall
2021-11-05 21:59 ` Julia Lawall [this message]
2021-11-06 15:36 ` [cocci] mm/slab: mass conversion of struct page to struct slab by spatch Markus Elfring
2021-11-07 12:10 ` [cocci] mm/slab: prepare for struct patch conversion " Markus Elfring
2021-11-07 12:22 ` Julia Lawall
2021-11-07 12:50 ` [cocci] mm/slab: prepare for struct page " Markus Elfring
2021-11-07 13:18 ` Julia Lawall
2021-11-07 13:40 ` Markus Elfring
2021-11-07 17:50 ` Vlastimil Babka
2021-11-07 18:09 ` Julia Lawall
2021-11-08 17:35 ` Markus Elfring
2021-11-08 17:40 ` Julia Lawall
2021-11-08 23:35 ` Vlastimil Babka
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.2111052256000.3000@hadrien \
--to=julia.lawall@inria.fr \
--cc=cocci@inria.fr \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).