OpenSBI Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: opensbi@lists.infradead.org
Subject: [PATCH v2] lib: sbi: Fix bug in strncmp function
Date: Thu, 05 Aug 2021 10:46:45 +0200	[thread overview]
Message-ID: <87bl6cth1m.fsf@igel.home> (raw)
In-Reply-To: <CAEUhbmVeLtGTbpbiO9we8vxmsV+HU1e-11kaS4VL_=XgOcBmvA@mail.gmail.com> (Bin Meng's message of "Thu, 5 Aug 2021 16:39:55 +0800")

On Aug 05 2021, Bin Meng wrote:

> Hi Dong,
>
> On Thu, Jul 29, 2021 at 12:23 AM Dong Du <Dd_nirvana@sjtu.edu.cn> wrote:
>>
>> No need to compare characters when the count turns to 0.
>> Fix the issue in sbi_strncmp.
>>
>> Signed-off-by: Dong Du <Dd_nirvana@sjtu.edu.cn>
>> ---
>>  lib/sbi/sbi_string.c | 4 ++++
>>  1 file changed, 4 insertions(+)
>>
>> diff --git a/lib/sbi/sbi_string.c b/lib/sbi/sbi_string.c
>> index 7805ba4..c87bce9 100644
>> --- a/lib/sbi/sbi_string.c
>> +++ b/lib/sbi/sbi_string.c
>> @@ -33,6 +33,10 @@ int sbi_strncmp(const char *a, const char *b, size_t count)
>>         for (; count > 0 && *a == *b && *a != '\0'; a++, b++, count--)
>>                 ;
>>
>> +       /* No difference till the end */
>> +       if (!count)
>> +               return 0;
>> +
>>         return *a - *b;
>>  }
>>
>
> Your original patch is also needed: "strncmp should return 0 when the
> count is 0"

Which this patch duly implements.

Andreas.

-- 
Andreas Schwab, schwab at linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."


  reply	other threads:[~2021-08-05  8:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 16:15 [PATCH v2] lib: sbi: Fix bug in strncmp function Dong Du
2021-08-05  8:39 ` Bin Meng
2021-08-05  8:46   ` Andreas Schwab [this message]
2021-08-05  9:18     ` Bin Meng
2021-08-07 10:18       ` Anup Patel

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=87bl6cth1m.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=opensbi@lists.infradead.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