linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: gregkh@linuxfoundation.org, davem@davemloft.net,
	len.baker@gmx.com, dave@stgolabs.net, edumazet@google.com,
	Haowen Bai <baihaowen@meizu.com>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] staging: rtl8192e: Fix signedness bug in rtllib_rx_assoc_resp()
Date: Fri, 15 Apr 2022 08:31:16 +0300	[thread overview]
Message-ID: <20220415053116.GN3293@kadam> (raw)
In-Reply-To: <8973092.rMLUfLXkoz@leap>

On Fri, Apr 15, 2022 at 07:22:36AM +0200, Fabio M. De Francesco wrote:
> On venerdì 15 aprile 2022 04:09:31 CEST Haowen Bai wrote:
> > function rtllib_rx_assoc_resp () unsigned errcode receive auth_parse()'s
> > errcode -ENOMEM.
> > 
> > Signed-off-by: Haowen Bai <baihaowen@meizu.com>
> > ---
> > V1->V2: reduce return random value; print its own error message.
> > 
> >  drivers/staging/rtl8192e/rtllib_softmac.c | 12 ++++++------
> >  1 file changed, 6 insertions(+), 6 deletions(-)
> > 
> 
> > [snip]
> 
> It looks like you are doing too many things and that those aren't even 
> discussed in your commit message.
> 

Nope.  The patch is one thing, but maybe it could be described better.
Here is my proposed commit message:

"The rtllib_rx_assoc_resp() function has a signedness bug because it's
a declared as a u16 but it return -ENOMEM.  When you look at it more
closely it returns a mix of error codes including 0xcafe, -ENOMEM, and
a->status which is WLAN_STATUS_NOT_SUPPORTED_AUTH_ALG.  This is a mess.

Clean it up to just return standard kernel error codes.  We can print
out the a->status before returning a regular error code.  The printks
in the caller need to be adjusted as well."

regards,
dan carpenter


  reply	other threads:[~2022-04-15  5:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15  2:09 [PATCH V2] staging: rtl8192e: Fix signedness bug in rtllib_rx_assoc_resp() Haowen Bai
2022-04-15  5:22 ` Fabio M. De Francesco
2022-04-15  5:31   ` Dan Carpenter [this message]
2022-04-15  5:50     ` [PATCH V3] " Haowen Bai
2022-04-15  6:06       ` Fabio M. De Francesco
2022-04-15  6:10         ` Fabio M. De Francesco
2022-04-15  6:15           ` [PATCH V4] " Haowen Bai
2022-04-15  6:20             ` Dan Carpenter
2022-04-15  6:39               ` Haowen Bai
2022-04-15  6:58                 ` Dan Carpenter
2022-04-15  7:21                   ` Haowen Bai
2022-04-20 16:41                     ` Greg Kroah-Hartman
2022-04-21  1:34                       ` Haowen Bai
2022-04-21  8:09                         ` kernel test robot
2022-04-21  8:21                           ` [PATCH V5] " Haowen Bai
2022-04-21 16:22                             ` Dan Carpenter
2022-04-18  1:48                   ` [PATCH V4] " baihaowen
2022-04-15  6:18       ` [PATCH V3] " Dan Carpenter
2022-04-15  5:25 ` [PATCH V2] " 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=20220415053116.GN3293@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=baihaowen@meizu.com \
    --cc=dave@stgolabs.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fmdefrancesco@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=len.baker@gmx.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    /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).