public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nicolas Iooss <nicolas.iooss_linux@m4x.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] staging: rtl8723bs: make memcmp() calls consistent
Date: Wed, 13 Dec 2017 12:47:28 +0100	[thread overview]
Message-ID: <20171213114728.GB21746@kroah.com> (raw)
In-Reply-To: <20171210193512.6309-1-nicolas.iooss_linux@m4x.org>

On Sun, Dec 10, 2017 at 08:35:12PM +0100, Nicolas Iooss wrote:
> rtw_pm_set() uses memcmp() with 5-chars strings and a length of 4 when
> parsing extra, and then parses extra+4 as an int:
> 
>     if (!memcmp(extra, "lps =", 4)) {
>         sscanf(extra+4, "%u", &mode);
>     /* ... */
>     } else if (!memcmp(extra, "ips =", 4)) {
>         sscanf(extra+4, "%u", &mode);
> 
> The space between the key ("lps" and "ips") and the equal sign seems
> suspicious. Remove it in order to make the calls to memcmp() consistent.

But you now just changing the parsing logic.  What broke because of
this?  Did you test this codepath with your patch?

I'm not disagreeing that this code seems really odd, but it must be
working as-is for someone, to change this logic will break their system
:(

thanks,

greg k-h

  reply	other threads:[~2017-12-13 11:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-10 19:35 [PATCH 1/1] staging: rtl8723bs: make memcmp() calls consistent Nicolas Iooss
2017-12-13 11:47 ` Greg Kroah-Hartman [this message]
2017-12-13 14:49   ` Hans de Goede
2017-12-13 15:12     ` Rasmus Villemoes
2017-12-13 16:00       ` Hans de Goede
2017-12-13 16:10     ` 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=20171213114728.GB21746@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.iooss_linux@m4x.org \
    /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