mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Andy Whitcroft <apw@shadowen.org>,
	linux-kernel@vger.kernel.org, Davidlohr Bueso <dbueso@suse.de>,
	Davidlohr Bueso <dave@stgolabs.net>
Subject: Re: [PATCH] checkpatch: Whine about ACCESS_ONCE
Date: Sun, 17 Apr 2016 01:27:51 -0700	[thread overview]
Message-ID: <1460881671.19090.90.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1604170743060.2068@localhost6.localdomain6>

On Sun, 2016-04-17 at 07:43 +0200, Julia Lawall wrote:
> On Sat, 16 Apr 2016, Joe Perches wrote:
> > On Sat, 2016-04-16 at 12:04 -0700, Joe Perches wrote:
> > > Add a test for use of ACCESS_ONCE that could be written using
> > > READ_ONCE or WRITE_ONCE.
> > > 
> > > --fix it too if desired.
> > 
> > And here's a simple coccinelle script that does a
> > rather better job:
> > 
> > $ cat access_once.cocci
> > @@
> > expression e1;
> > expression e2;
> > @@
> > 
> > -     ACCESS_ONCE(e1) = e2
> > +     WRITE_ONCE(e1, e2)
> > 
> > @@
> > expression e1;
> > @@
> > 
> > -     ACCESS_ONCE(e1)
> > +     READ_ONCE(e1)
> 
> Looks good to me.  Is this something to put in the kernel?

Maybe.  There are more than 500 of these ACCESS_ONCE
uses that could be converted.

The kernel cocci scripts are typically more complicated
with virtual org/report/context/patch blocks.

So perhaps this needs to be fleshed out more.

Works for me as-is though.

  reply	other threads:[~2016-04-17  8:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-16 17:34 [PATCH -next] kernel: Replace ACCESS_ONCE with READ/WRITE_ONCE Davidlohr Bueso
2016-04-16 19:04 ` [PATCH] checkpatch: Whine about ACCESS_ONCE Joe Perches
2016-04-16 19:48   ` Joe Perches
2016-04-17  5:43     ` Julia Lawall
2016-04-17  8:27       ` Joe Perches [this message]
2016-04-17 11:17         ` Julia Lawall
2016-04-17 11:39         ` Julia Lawall
2016-04-17 16:02           ` Joe Perches
     [not found]             ` <alpine.DEB.2.02.1604171944500.2004@localhost6.localdomain6>
     [not found]               ` <1460915801.19090.100.camel@perches.com>
     [not found]                 ` <alpine.DEB.2.02.1604172001410.2004@localhost6.localdomain6>
2016-04-19 19:12                   ` coccinelle: bool if (foo) return true; else return false; Joe Perches
2016-04-19 19:15                     ` Julia Lawall
2016-04-20  7:19                       ` [Cocci] " Michael Stefaniuc
2016-04-20  7:25                         ` Joe Perches
2016-04-17 17:26   ` [PATCH V2] checkpatch: Whine about ACCESS_ONCE Joe Perches

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=1460881671.19090.90.camel@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=dave@stgolabs.net \
    --cc=dbueso@suse.de \
    --cc=julia.lawall@lip6.fr \
    --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

Powered by JetHome