From: Joe Perches <joe@perches.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Nicholas Mc Guire <hofrat@osadl.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Whitcroft <apw@canonical.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: match more world writable permissions
Date: Sat, 14 Mar 2015 08:42:09 -0700 [thread overview]
Message-ID: <1426347729.2744.3.camel@perches.com> (raw)
In-Reply-To: <20150314143200.GA19645@roeck-us.net>
On Sat, 2015-03-14 at 07:32 -0700, Guenter Roeck wrote:
> On Fri, Mar 13, 2015 at 04:43:43PM -0700, Joe Perches wrote:
> > Currently checkpatch will fuss if one uses world writable
> > settings in debugfs files and DEVICE_ATTR uses by testing
> > S_IWUGO but not testing S_IWOTH, S_IRWXUGO or S_IALLUGO.
> >
> > Extend the check to catch all cases exporting world writable
> > permissions including octal values.
> >
> > Original-patch-by: Nicholas Mc Guire <hofrat@osadl.org>
> > Signed-off-by: Joe Perches <joe@perches.com>
> > ---
> > scripts/checkpatch.pl | 12 ++++++++++--
> > 1 file changed, 10 insertions(+), 2 deletions(-)
> >
> > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > index 6b79beb..4f07d50 100755
> > --- a/scripts/checkpatch.pl
> > +++ b/scripts/checkpatch.pl
> > @@ -443,6 +443,14 @@ foreach my $entry (@mode_permission_funcs) {
> > $mode_perms_search .= $entry->[0];
> > }
> >
> > +$our $mode_perms_world_writable = qr{
> > + S_IWUGO |
> > + S_IWOTH |
> > + S_IRWXUGO |
> > + S_IALLUGO |
> > + 0[0-7][0-7][2367]
> > +}x;
> > +
> > our $allowed_asm_includes = qr{(?x:
> > irq|
> > memory|
> > @@ -5356,8 +5364,8 @@ sub process {
> > }
> > }
> >
> > - if ($line =~ /debugfs_create_file.*S_IWUGO/ ||
> > - $line =~ /DEVICE_ATTR.*S_IWUGO/ ) {
> > + if ($line =~ /debugfs_create_\w+.*\b$mode_perms_world_writable\b/ ||
> > + $line =~ /DEVICE_ATTR.*\b$mode_perms_world_writable\b/) {
> > WARN("EXPORTED_WORLD_WRITABLE",
> > "Exporting world writable files is usually an error. Consider more restrictive permissions.\n" . $herecurr);
>
> With https://lkml.org/lkml/2015/3/12/412 in mind, maybe this should be
> marked as error, at least for sysfs attributes.
Maybe it's time for the debate this commit referenced:
commit 58f86cc89c3372d3e61d5b71e5513ec5a0b02848
Author: Rusty Russell <rusty@rustcorp.com.au>
Date: Mon Mar 24 12:00:34 2014 +1030
VERIFY_OCTAL_PERMISSIONS: stricter checking for sysfs perms.
Summary of http://lkml.org/lkml/2014/3/14/363 :
Ted: module_param(queue_depth, int, 444)
Joe: 0444!
Rusty: User perms >= group perms >= other perms?
Joe: CLASS_ATTR, DEVICE_ATTR, SENSOR_ATTR and SENSOR_ATTR_2?
Side effect of stricter permissions means removing the unnecessary
S_IFREG from several callers.
Note that the BUILD_BUG_ON_ZERO((perm) & 2) test was removed: a fair
number of drivers fail this test, so that will be the debate for a
future patch.
next prev parent reply other threads:[~2015-03-14 15:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 19:23 [PATCH] checkpatch: catch all world writable debugfs_create_file Nicholas Mc Guire
2015-03-13 20:16 ` Joe Perches
2015-03-13 20:42 ` Joe Perches
2015-03-13 23:43 ` [PATCH] checkpatch: match more world writable permissions Joe Perches
2015-03-14 7:35 ` Nicholas Mc Guire
2015-03-14 14:32 ` Guenter Roeck
2015-03-14 15:42 ` Joe Perches [this message]
2015-03-17 23:17 ` Andrew Morton
2015-03-18 5:56 ` 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=1426347729.2744.3.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=hofrat@osadl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.