LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Evgeniy Polyakov <zbr@ioremap.net>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2] w1: Misuse of get_user()/put_user() reported by sparse
Date: Fri, 26 Nov 2021 17:57:58 +0100	[thread overview]
Message-ID: <8e5493ac-dd05-9bad-c9ae-169114e0fdcf@csgroup.eu> (raw)
In-Reply-To: <YaERVtyYpJ+BTQ/f@kroah.com>



Le 26/11/2021 à 17:54, Greg Kroah-Hartman a écrit :
> On Fri, Nov 26, 2021 at 05:47:58PM +0100, Christophe Leroy wrote:
>> sparse warnings: (new ones prefixed by >>)
>>>> drivers/w1/slaves/w1_ds28e04.c:342:13: sparse: sparse: incorrect type in initializer (different address spaces) @@     expected char [noderef] __user *_pu_addr @@     got char *buf @@
>>     drivers/w1/slaves/w1_ds28e04.c:342:13: sparse:     expected char [noderef] __user *_pu_addr
>>     drivers/w1/slaves/w1_ds28e04.c:342:13: sparse:     got char *buf
>>>> drivers/w1/slaves/w1_ds28e04.c:356:13: sparse: sparse: incorrect type in initializer (different address spaces) @@     expected char const [noderef] __user *_gu_addr @@     got char const *buf @@
>>     drivers/w1/slaves/w1_ds28e04.c:356:13: sparse:     expected char const [noderef] __user *_gu_addr
>>     drivers/w1/slaves/w1_ds28e04.c:356:13: sparse:     got char const *buf
>>
>> The buffer buf is a failsafe buffer in kernel space, it's not user
>> memory hence doesn't deserve the use of get_user() or put_user().
>>
>> Access 'buf' content directly.
>>
>> Reported-by: kernel test robot <lkp@intel.com>
>> Link: https://lore.kernel.org/lkml/202111190526.K5vb7NWC-lkp@intel.com/T/
>> Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
>> ---
>> v2: Use sysfs_emit() and kstrtobool()
>> ---
>>   drivers/w1/slaves/w1_ds28e04.c | 25 +++----------------------
>>   1 file changed, 3 insertions(+), 22 deletions(-)
>>
>> diff --git a/drivers/w1/slaves/w1_ds28e04.c b/drivers/w1/slaves/w1_ds28e04.c
>> index e4f336111edc..98f80f412cfd 100644
>> --- a/drivers/w1/slaves/w1_ds28e04.c
>> +++ b/drivers/w1/slaves/w1_ds28e04.c
>> @@ -32,7 +32,7 @@ static int w1_strong_pullup = 1;
>>   module_param_named(strong_pullup, w1_strong_pullup, int, 0);
>>   
>>   /* enable/disable CRC checking on DS28E04-100 memory accesses */
>> -static char w1_enable_crccheck = 1;
>> +static bool w1_enable_crccheck = true;
>>   
>>   #define W1_EEPROM_SIZE		512
>>   #define W1_PAGE_COUNT		16
>> @@ -339,32 +339,13 @@ static BIN_ATTR_RW(pio, 1);
>>   static ssize_t crccheck_show(struct device *dev, struct device_attribute *attr,
>>   			     char *buf)
>>   {
>> -	if (put_user(w1_enable_crccheck + 0x30, buf))
>> -		return -EFAULT;
>> -
>> -	return sizeof(w1_enable_crccheck);
>> +	return sysfs_emit(buf, "%d\n", w1_enable_crccheck);
>>   }
>>   
>>   static ssize_t crccheck_store(struct device *dev, struct device_attribute *attr,
>>   			      const char *buf, size_t count)
>>   {
>> -	char val;
>> -
>> -	if (count != 1 || !buf)
>> -		return -EINVAL;
>> -
>> -	if (get_user(val, buf))
>> -		return -EFAULT;
>> -
>> -	/* convert to decimal */
>> -	val = val - 0x30;
>> -	if (val != 0 && val != 1)
>> -		return -EINVAL;
>> -
>> -	/* set the new value */
>> -	w1_enable_crccheck = val;
>> -
>> -	return sizeof(w1_enable_crccheck);
>> +	return kstrtobool(buf, &w1_enable_crccheck) ? : count;
> 
> Please spell this line out, using ? : is unreadable at times.
> 

You prefer something like:

	int err = kstrtobool(buf, &w1_enable_crccheck);

	return err ? err : count;


Or

	int err = kstrtobool(buf, &w1_enable_crccheck);

	if (err)
		return err;

	return count;

?

  reply	other threads:[~2021-11-26 16:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-26 16:47 [PATCH v2] w1: Misuse of get_user()/put_user() reported by sparse Christophe Leroy
2021-11-26 16:54 ` Greg Kroah-Hartman
2021-11-26 16:57   ` Christophe Leroy [this message]
2021-11-26 17:02     ` 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=8e5493ac-dd05-9bad-c9ae-169114e0fdcf@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lkp@intel.com \
    --cc=zbr@ioremap.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox