From: Shuah Khan <skhan@linuxfoundation.org>
To: Guo Zhengkui <guozhengkui@vivo.com>,
Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Cc: zhengkui_guo@outlook.com, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH linux-next] selftests/proc: fix array_size.cocci warning
Date: Tue, 22 Mar 2022 17:02:11 -0600 [thread overview]
Message-ID: <eb5dd04b-a20c-1874-e71e-60c962ad8dcb@linuxfoundation.org> (raw)
In-Reply-To: <20220321102546.12569-1-guozhengkui@vivo.com>
On 3/21/22 4:25 AM, Guo Zhengkui wrote:
> Fix the following coccicheck warning:
>
> tools/testing/selftests/proc/proc-pid-vm.c:371:26-27:
> WARNING: Use ARRAY_SIZE
> tools/testing/selftests/proc/proc-pid-vm.c:420:26-27:
> WARNING: Use ARRAY_SIZE
>
> It has been tested with gcc (Debian 8.3.0-6) 8.3.0 on x86_64.
>
> Signed-off-by: Guo Zhengkui <guozhengkui@vivo.com>
> ---
> tools/testing/selftests/proc/proc-pid-vm.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/proc/proc-pid-vm.c b/tools/testing/selftests/proc/proc-pid-vm.c
> index 18a3bde8bc96..28604c9f805c 100644
> --- a/tools/testing/selftests/proc/proc-pid-vm.c
> +++ b/tools/testing/selftests/proc/proc-pid-vm.c
> @@ -46,6 +46,8 @@
> #include <sys/time.h>
> #include <sys/resource.h>
>
> +#include "../kselftest.h"
> +
> static inline long sys_execveat(int dirfd, const char *pathname, char **argv, char **envp, int flags)
> {
> return syscall(SYS_execveat, dirfd, pathname, argv, envp, flags);
> @@ -368,7 +370,7 @@ int main(void)
> };
> int i;
>
> - for (i = 0; i < sizeof(S)/sizeof(S[0]); i++) {
> + for (i = 0; i < ARRAY_SIZE(S); i++) {
> assert(memmem(buf, rv, S[i], strlen(S[i])));
> }
>
> @@ -417,7 +419,7 @@ int main(void)
> };
> int i;
>
> - for (i = 0; i < sizeof(S)/sizeof(S[0]); i++) {
> + for (i = 0; i < ARRAY_SIZE(S); i++) {
> assert(memmem(buf, rv, S[i], strlen(S[i])));
> }
> }
>
Looks good to me. I will apply this once merge window closes.
thanks,
-- Shuah
prev parent reply other threads:[~2022-03-22 23:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 10:25 [PATCH linux-next] selftests/proc: fix array_size.cocci warning Guo Zhengkui
2022-03-22 23:02 ` 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=eb5dd04b-a20c-1874-e71e-60c962ad8dcb@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=guozhengkui@vivo.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=zhengkui_guo@outlook.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