From: Joe Perches <joe@perches.com>
To: Denis Efremov <efremov@linux.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
"Gustavo A . R . Silva" <gustavoars@kernel.org>,
Julia Lawall <julia.lawall@inria.fr>,
Alex Dewar <alex.dewar90@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] sysfs: Add sysfs_emit and sysfs_emit_at to format sysfs output
Date: Sun, 30 Aug 2020 09:05:13 -0700 [thread overview]
Message-ID: <09bacd3b3da948df632a0ffb4d7ca90603a45d06.camel@perches.com> (raw)
In-Reply-To: <8b01dc3a-3642-bc12-ae4d-42b90ec208f1@linux.com>
On Sun, 2020-08-30 at 18:25 +0300, Denis Efremov wrote:
>
> On 8/30/20 3:43 AM, Joe Perches wrote:
> > $ cat sysfs_emit.cocci
> > @@
> > identifier d_show =~ "^.*show.*$";
>
> I think this additional pattern will allow to take more functions into the scope.
>
> @da@
> identifier show, store;
> expression name, mode;
> @@
>
> (
> DEVICE_ATTR(name, mode, show, store)
> DEVICE_ATTR_PREALLOC(name, mode, show, store)
> DEVICE_ATTR_IGNORE_LOCKDEP(name, mode, show, store)
> )
Thanks Denis.
I'll try that out too.
A trivial grep shows there are at least 130+
DEVICE_ATTR functions that have a show function
that doesn't include "show" in the function name.
$ grep-2.5.4 -rP --include=*.[ch] '\bDEVICE_ATTR\s*\(\s*\w+\s*,\s*[^,]+,\s*[^,]*,[^;]+;' * | \
perl -p -e 's/[[:space:]]*//g; s/;/;\n/g' | \
cut -f3 -d, | \
grep -v show | \
sort | uniq | wc -l
139
> @@
> // I think device_show_ulong, device_show_int, device_show_bool
> // functions deserve explicit handling because they are somewhat
> // reference implementations.
Those reference implementations could be send as
a separate patch but this preliminary script does
already handle them.
I do like the idea below of renaming the show
functions without _show in the name adding _show.
> identifier d_show = { da.show, device_show_ulong, device_show_int, device_show_bool };
> identifier dev, attr, buf;
> @@
>
> * ssize_t d_show(struct device *dev, struct device_attribute *attr, char *buf)
> {
> ...
> }
>
>
> I tried also to handle DEVICE_ATTR_RW, but I failed to use fresh identifier.
> This doesn't work:
>
> @darw@
> identifier name;
> @@
>
> (
> DEVICE_ATTR_RW(name)
> DEVICE_ATTR_RO(name)
> DEVICE_ATTR_WO(name)
> )
>
> @@
> identifier darw.name;
> fresh identifier d_show = name ## "_show"; // <== parse error
> identifier dev, attr, buf;
> @@
>
> * ssize_t d_show(struct device *dev, struct device_attribute *attr, char *buf)
> {
> ...
> }
>
>
> Regards,
> Denis
next prev parent reply other threads:[~2020-08-30 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 23:48 [PATCH V2] sysfs: Add sysfs_emit and sysfs_emit_at to format sysfs output Joe Perches
2020-08-30 0:43 ` Joe Perches
2020-08-30 8:59 ` Julia Lawall
2020-08-30 15:25 ` Denis Efremov
2020-08-30 16:05 ` Joe Perches [this message]
2020-09-07 13:36 ` Greg Kroah-Hartman
2020-09-06 17:24 ` Joe Perches
2020-09-07 5:48 ` Greg Kroah-Hartman
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=09bacd3b3da948df632a0ffb4d7ca90603a45d06.camel@perches.com \
--to=joe@perches.com \
--cc=alex.dewar90@gmail.com \
--cc=corbet@lwn.net \
--cc=efremov@linux.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=julia.lawall@inria.fr \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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