public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Oberparleiter <oberpar@linux.ibm.com>
To: Chuhong Yuan <hslester96@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 02/10] gcov: Replace strncmp with str_has_prefix
Date: Fri, 2 Aug 2019 13:45:31 +0200	[thread overview]
Message-ID: <be8f4deb-7e7e-ee5d-a026-a6f5ab5f728a@linux.ibm.com> (raw)
In-Reply-To: <20190802014650.8735-1-hslester96@gmail.com>

On 02.08.2019 03:46, Chuhong Yuan wrote:
> strncmp(str, const, len) is error-prone because len
> is easy to have typo.
> The example is the hard-coded len has counting error
> or sizeof(const) forgets - 1.
> So we prefer using newly introduced str_has_prefix
> to substitute such strncmp.
> 
> Signed-off-by: Chuhong Yuan <hslester96@gmail.com>

Looks sane!

Acked-by: Peter Oberparleiter <oberpar@linux.ibm.com>

> ---
> Changes in v2:
>   - Revise the description.
> 
>  kernel/gcov/fs.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/gcov/fs.c b/kernel/gcov/fs.c
> index e5eb5ea7ea59..67296c1768b4 100644
> --- a/kernel/gcov/fs.c
> +++ b/kernel/gcov/fs.c
> @@ -354,7 +354,7 @@ static char *get_link_target(const char *filename, const struct gcov_link *ext)
>   */
>  static const char *deskew(const char *basename)
>  {
> -	if (strncmp(basename, SKEW_PREFIX, sizeof(SKEW_PREFIX) - 1) == 0)
> +	if (str_has_prefix(basename, SKEW_PREFIX))
>  		return basename + sizeof(SKEW_PREFIX) - 1;
>  	return basename;
>  }
> 


-- 
Peter Oberparleiter
Linux on Z Development - IBM Germany


      reply	other threads:[~2019-08-02 11:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02  1:46 [PATCH v2 02/10] gcov: Replace strncmp with str_has_prefix Chuhong Yuan
2019-08-02 11:45 ` Peter Oberparleiter [this message]

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=be8f4deb-7e7e-ee5d-a026-a6f5ab5f728a@linux.ibm.com \
    --to=oberpar@linux.ibm.com \
    --cc=hslester96@gmail.com \
    --cc=linux-kernel@vger.kernel.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