From: Longsuhui <Jack_sun@tom.com>
To: Guenter Roeck <linux@roeck-us.net>, Su Hui <suhui@nfschina.com>
Cc: Jeremy Kerr <jk@ozlabs.org>, Joel Stanley <joel@jms.id.au>,
Alistar Popple <alistair@popple.id.au>,
Eddie James <eajames@linux.ibm.com>,
eajames@us.ibm.com, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org, cbostic@linux.vnet.ibm.com,
linux-fsi@lists.ozlabs.org
Subject: Re: [PATCH] drivers/fsi/scom: Return -EFAULT if copy fails
Date: Tue, 23 May 2023 12:32:11 +0800 [thread overview]
Message-ID: <7f1cd0ad-7991-af0c-a31a-84c261d4ca18@tom.com> (raw)
In-Reply-To: <de9a7ffe-bedd-4181-886d-c9a3006b7be8@roeck-us.net>
On 2023/5/23 06:30, Guenter Roeck wrote:
> On Fri, May 19, 2023 at 09:37:10AM +0800, Su Hui wrote:
>> The copy_to/from_user() functions return the number of bytes remaining
>> to be copied, but we want to return -EFAULT to the user.
>>
> Why ? EFAULT means that a bad address was provided, and it is not
> immediately obvious why that would be the case.
When copy_to/from_user() functions failed, the error code is -EFAULT in most case.
git grep -A1 "copy_from_user" | grep EFAULT | wc -l
1985
git grep -A1 "copy_to_user" | grep EFAULT | wc -l
1871
I think return -EFAULT is also right in this case.
Su Hui
> Guenter
>
>> Fixes: 680ca6dcf5c2 ("drivers/fsi: Add SCOM FSI client device driver")
>> Signed-off-by: Su Hui <suhui@nfschina.com>
>> ---
>> drivers/fsi/fsi-scom.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/fsi/fsi-scom.c b/drivers/fsi/fsi-scom.c
>> index bcb756dc9866..caaf7738eb98 100644
>> --- a/drivers/fsi/fsi-scom.c
>> +++ b/drivers/fsi/fsi-scom.c
>> @@ -335,7 +335,7 @@ static ssize_t scom_read(struct file *filep, char __user *buf, size_t len,
>> if (rc)
>> dev_dbg(dev, "copy to user failed:%d\n", rc);
>>
>> - return rc ? rc : len;
>> + return rc ? -EFAULT : len;
>> }
>>
>> static ssize_t scom_write(struct file *filep, const char __user *buf,
>> --
>> 2.30.2
>>
next prev parent reply other threads:[~2023-05-23 4:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 1:37 Su Hui
2023-05-22 22:30 ` Guenter Roeck
2023-05-23 4:32 ` Longsuhui [this message]
2023-05-23 7:05 ` Dan Carpenter
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=7f1cd0ad-7991-af0c-a31a-84c261d4ca18@tom.com \
--to=jack_sun@tom.com \
--cc=alistair@popple.id.au \
--cc=cbostic@linux.vnet.ibm.com \
--cc=eajames@linux.ibm.com \
--cc=eajames@us.ibm.com \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fsi@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=suhui@nfschina.com \
/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
all inboxes | Powered by JetHome®