From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
kernel <kernel@savoirfairelinux.com>
Subject: Re: [PATCH 2/3] sysfs: Only accept read/write permissions for file attributes
Date: Mon, 19 Jan 2015 19:07:18 -0500 (EST) [thread overview]
Message-ID: <643183939.413796.1421712438502.JavaMail.root@mail> (raw)
In-Reply-To: <1421703806-29791-3-git-send-email-linux@roeck-us.net>
Hi Guenter,
> For sysfs file attributes, only read and write permisssions make sense.
Minor typo, there's an extra 's' to permissions.
> Mask provided attribute permissions accordingly and send a warning
> to the console if invalid permission bits are set.
>
> Cc: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> ---
> fs/sysfs/group.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/fs/sysfs/group.c b/fs/sysfs/group.c
> index 305eccb..0de6473 100644
> --- a/fs/sysfs/group.c
> +++ b/fs/sysfs/group.c
> @@ -55,6 +55,12 @@ static int create_files(struct kernfs_node *parent, struct kobject *kobj,
> if (!mode)
> continue;
> }
> +
> + WARN(mode & ~(S_IRUGO | S_IWUGO | SYSFS_PREALLOC),
> + "Attribute %s: Invalid permission 0x%x\n",
> + (*attr)->name, mode);
To print permissions, I would suggest unsigned octal ("0%o").
> +
> + mode &= S_IRUGO | S_IWUGO | SYSFS_PREALLOC;
As readable attributes are created with S_IRUGO and writable attributes are
created with S_IWUSR, I would limit the scope of is_visible to only:
S_IRUGO | S_IWUSR. Write permission for group and others feels wrong.
Then, I think we may want to keep the extra bits (all mode bits > 0777) from
the default attribute mode. Can they be used for sysfs attributes?
My suggestion is something like this:
/* Limit the scope to S_IRUGO | S_IWUSR */
if (mode & ~(S_IRUGO | S_IWUSR))
pr_warn("Attribute %s: Invalid permissions 0%o\n",
(*attr)->name, mode);
mode &= S_IRUGO | S_IWUSR;
/* Use only returned bits and defaults > 0777 */
mode |= (*attr)->mode & ~S_IRWXUGO;
> error = sysfs_add_file_mode_ns(parent, *attr, false,
> mode, NULL);
> if (unlikely(error))
The code hitting this warning actually is drivers/pci/pci-sysfs.c, which
declares write-only attributes with S_IWUSR|S_IWGRP (0220). Is that correct to
have write access for group for these attributes?
Thanks,
-v
next prev parent reply other threads:[~2015-01-20 0:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 21:43 [PATCH 0/3] sysfs: Refine is_visible API Guenter Roeck
2015-01-19 21:43 ` [PATCH 1/3] sysfs: Use only return value from is_visible for the file mode Guenter Roeck
2015-01-19 21:43 ` [PATCH 2/3] sysfs: Only accept read/write permissions for file attributes Guenter Roeck
2015-01-20 0:07 ` Vivien Didelot [this message]
2015-01-20 2:42 ` Guenter Roeck
2015-01-20 15:44 ` Vivien Didelot
2015-01-20 17:13 ` Guenter Roeck
2015-01-20 19:51 ` Greg Kroah-Hartman
2015-01-19 21:43 ` [PATCH 3/3] sysfs: Document struct attribute_group Guenter Roeck
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=643183939.413796.1421712438502.JavaMail.root@mail \
--to=vivien.didelot@savoirfairelinux.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@savoirfairelinux.com \
--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.