linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, nicholas.johnson-opensource@outlook.com.au
Subject: Re: [PATCH 3/3] nvmem: core: use is_bin_visible for permissions
Date: Wed, 25 Mar 2020 09:15:39 +0000	[thread overview]
Message-ID: <efa9f7c5-f96c-5dcd-26ea-397997b5b5c0@linaro.org> (raw)
In-Reply-To: <20200324174642.GA2524667@kroah.com>



On 24/03/2020 17:46, Greg KH wrote:
> On Tue, Mar 24, 2020 at 05:16:00PM +0000, Srinivas Kandagatla wrote:
>> By using is_bin_visible callback to set permissions will remove a large list
>> of attribute groups. These group permissions can be dynamically derived in
>> the callback.
>>
>> Suggested-by: Greg KH <gregkh@linuxfoundation.org>
>> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
>> ---
>>   drivers/nvmem/nvmem-sysfs.c | 74 +++++++++----------------------------
>>   1 file changed, 18 insertions(+), 56 deletions(-)
>>
>> diff --git a/drivers/nvmem/nvmem-sysfs.c b/drivers/nvmem/nvmem-sysfs.c
>> index 8759c4470012..1ff1801048f6 100644
>> --- a/drivers/nvmem/nvmem-sysfs.c
>> +++ b/drivers/nvmem/nvmem-sysfs.c
>> @@ -103,6 +103,17 @@ static ssize_t bin_attr_nvmem_write(struct file *filp, struct kobject *kobj,
>>   
>>   	return count;
>>   }
>> +static umode_t nvmem_bin_attr_is_visible(struct kobject *kobj,
>> +					 struct bin_attribute *attr, int i)
>> +{
>> +	struct device *dev = container_of(kobj, struct device, kobj);
>> +	struct nvmem_device *nvmem = to_nvmem_device(dev);
>> +
>> +	if (nvmem->root_only)
>> +		return nvmem->read_only ? 0400 : 0600;
>> +
>> +	return nvmem->read_only ? 0444 : 0644;
>> +}
> 
> I don't know why this is so hard for me to read, but how about this
> instead:
> 
> static umode_t nvmem_bin_attr_is_visible(struct kobject *kobj,
> 					 struct bin_attribute *attr, int i)
> {
> 	struct device *dev = container_of(kobj, struct device, kobj);
> 	struct nvmem_device *nvmem = to_nvmem_device(dev);
> 	umode_t mode = 0400;
> 
> 	if (!nvmem->root_only)
> 		mode |= 0044;
> 
> 	if (!nvmem->read_only)
> 		mode |= 0200;
> 
> 	return mode;
> }
> 
> Did I get the logic corect?

That looks perfect and matches what is in upstream!
Thanks for suggesting this cleanup!

I will send v2 with this change!

--srini
> 
> thanks,
> 
> greg k-h
> 

  reply	other threads:[~2020-03-25  9:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24 17:15 [PATCH 0/3] nvmem: use is_bin_visible callback Srinivas Kandagatla
2020-03-24 17:15 ` [PATCH 1/3] nvmem: core: use device_register and device_unregister Srinivas Kandagatla
2020-03-24 17:15 ` [PATCH 2/3] nvmem: core: add root_only member to nvmem device struct Srinivas Kandagatla
2020-03-24 17:16 ` [PATCH 3/3] nvmem: core: use is_bin_visible for permissions Srinivas Kandagatla
2020-03-24 17:46   ` Greg KH
2020-03-25  9:15     ` Srinivas Kandagatla [this message]
2020-03-24 23:05   ` Nicholas Johnson
2020-03-25  7:36     ` gregkh
2020-03-25  9:36     ` Srinivas Kandagatla
2020-03-24 17:58 ` [PATCH 0/3] nvmem: use is_bin_visible callback Greg KH

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=efa9f7c5-f96c-5dcd-26ea-397997b5b5c0@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicholas.johnson-opensource@outlook.com.au \
    /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).