All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Haowen Bai <baihaowen@meizu.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4] staging: rtl8192e: Fix signedness bug in rtllib_rx_assoc_resp()
Date: Wed, 20 Apr 2022 18:41:26 +0200	[thread overview]
Message-ID: <YmA3ttZal8Bwlp7P@kroah.com> (raw)
In-Reply-To: <1650007296-31508-1-git-send-email-baihaowen@meizu.com>

On Fri, Apr 15, 2022 at 03:21:35PM +0800, Haowen Bai wrote:
> 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.
> 
> Signed-off-by: Haowen Bai <baihaowen@meizu.com>
> ---
> V1->V2: reduce return random value; print its own error message.
> V2->V3: change commit message; change s16 -> int.
> V3->V4: add message suggested by Dan Carpenter. If you look up what 
> a->status is, it can only be WLAN_STATUS_NOT_SUPPORTED_AUTH_ALG which 
> is not worth preserving really.

I see 3 different v4 patches.  Obviously something went wrong, please
submit a new one, and properly number it and say what changed between
them all.

thanks,

greg k-h

  reply	other threads:[~2022-04-20 16:41 UTC|newest]

Thread overview: 21+ 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
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 [this message]
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  8:21                             ` Haowen Bai
2022-04-21 16:22                             ` Dan Carpenter
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=YmA3ttZal8Bwlp7P@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=baihaowen@meizu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.