From: Shuah Khan <shuah@kernel.org>
To: Anders Roxell <anders.roxell@linaro.org>, trenn@suse.com
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH v2] cpupower: remove stringop-truncation waring
Date: Tue, 28 Aug 2018 15:48:20 -0600 [thread overview]
Message-ID: <a886478f-e068-415a-44b6-e31a6d593a48@kernel.org> (raw)
In-Reply-To: <20180828093118.28326-1-anders.roxell@linaro.org>
On 08/28/2018 03:31 AM, Anders Roxell wrote:
> The strncpy doesn't null terminate the string because the size is too
> short by one byte.
>
> parse.c: In function ‘prepare_default_config’:
> parse.c:148:2: warning: ‘strncpy’ output truncated before terminating
> nul copying 8 bytes from a string of the same length
> [-Wstringop-truncation]
> strncpy(config->governor, "ondemand", 8);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> The normal method of passing the length of the destination buffer works
> correctly here.
>
> Fixes: 7fe2f6399a84 ("cpupowerutils - cpufrequtils extended with quite some features")
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
> ---
> tools/power/cpupower/bench/parse.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/power/cpupower/bench/parse.c b/tools/power/cpupower/bench/parse.c
> index 9ba8a44ad2a7..84caee38418f 100644
> --- a/tools/power/cpupower/bench/parse.c
> +++ b/tools/power/cpupower/bench/parse.c
> @@ -145,7 +145,7 @@ struct config *prepare_default_config()
> config->cpu = 0;
> config->prio = SCHED_HIGH;
> config->verbose = 0;
> - strncpy(config->governor, "ondemand", 8);
> + strncpy(config->governor, "ondemand", sizeof(config->governor));
>
> config->output = stdout;
>
>
Thanks. Applied to cpupower git for 4.19-rc3
thanks,
-- Shuah
prev parent reply other threads:[~2018-08-28 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 12:02 [PATCH] " Anders Roxell
2018-08-27 17:46 ` Shuah Khan
2018-08-28 9:31 ` [PATCH v2] " Anders Roxell
2018-08-28 21:48 ` Shuah Khan [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=a886478f-e068-415a-44b6-e31a6d593a48@kernel.org \
--to=shuah@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=trenn@suse.com \
/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
all inboxes | Powered by JetHome®