public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <simon.horman@corigine.com>
To: Wei Chen <harperchen1110@gmail.com>
Cc: pkshih@realtek.com, kvalo@kernel.org, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wireless: rtlwifi: fix incorrect error codes in rtl_debugfs_set_write_rfreg()
Date: Sat, 25 Mar 2023 10:47:54 +0100	[thread overview]
Message-ID: <ZB7DSn3wfjU9OVgJ@corigine.com> (raw)
In-Reply-To: <20230325083429.3571917-1-harperchen1110@gmail.com>

On Sat, Mar 25, 2023 at 08:34:29AM +0000, Wei Chen wrote:
> If there is a failure during copy_from_user or user-provided data buffer
> is invalid, rtl_debugfs_set_write_rfreg should return negative error code
> instead of a positive value count.
> 
> Fix this bug by returning correct error code. Moreover, the check of buffer
> against null is removed since it will be handled by copy_from_user.
> 
> Signed-off-by: Wei Chen <harperchen1110@gmail.com>

Hi Wei Chen,

* I'm not sure if a fixes tag is appropriate for this.
  But if so, perhaps it should be:

  Fixes: 610247f46feb ("rtlwifi: Improve debugging by using debugfs")

* I think the preferred subject prefix may be                                     'rtlwifi: ' (without the leading 'wireless: ').

* This seems to be v2 of this patch, which would be best noted in
  the subject '[PATCH v2]'.               

The above notwithstanding, the code changes look correct to me.

Reviewed-by: Simon Horman <simon.horman@corigine.com>

> ---
>  drivers/net/wireless/realtek/rtlwifi/debug.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/net/wireless/realtek/rtlwifi/debug.c b/drivers/net/wireless/realtek/rtlwifi/debug.c
> index 3e7f9b4f1f19..9eb26dfe4ca9 100644
> --- a/drivers/net/wireless/realtek/rtlwifi/debug.c
> +++ b/drivers/net/wireless/realtek/rtlwifi/debug.c
> @@ -375,8 +375,8 @@ static ssize_t rtl_debugfs_set_write_rfreg(struct file *filp,
>  
>  	tmp_len = (count > sizeof(tmp) - 1 ? sizeof(tmp) - 1 : count);
>  
> -	if (!buffer || copy_from_user(tmp, buffer, tmp_len))
> -		return count;
> +	if (copy_from_user(tmp, buffer, tmp_len))
> +		return -EFAULT;
>  
>  	tmp[tmp_len] = '\0';
>  
> @@ -386,7 +386,7 @@ static ssize_t rtl_debugfs_set_write_rfreg(struct file *filp,
>  	if (num != 4) {
>  		rtl_dbg(rtlpriv, COMP_ERR, DBG_DMESG,
>  			"Format is <path> <addr> <mask> <data>\n");
> -		return count;
> +		return -EINVAL;
>  	}
>  
>  	rtl_set_rfreg(hw, path, addr, bitmask, data);
> -- 
> 2.25.1
> 

  reply	other threads:[~2023-03-25  9:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-25  8:34 [PATCH] wireless: rtlwifi: fix incorrect error codes in rtl_debugfs_set_write_rfreg() Wei Chen
2023-03-25  9:47 ` Simon Horman [this message]
2023-03-26  5:47   ` Wei Chen
2023-03-26  8:03     ` Simon Horman
2023-03-26 17:32       ` Larry Finger

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=ZB7DSn3wfjU9OVgJ@corigine.com \
    --to=simon.horman@corigine.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=harperchen1110@gmail.com \
    --cc=kuba@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pkshih@realtek.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