linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
	Shuah Khan <shuah@kernel.org>,
	linux-kernel@vger.kernel.org, Peter Xu <peterx@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v1 1/1] selftests: mm: uufd-unit-tests: remove a format warning in printf
Date: Sun, 11 Jun 2023 17:30:22 +0500	[thread overview]
Message-ID: <109d9c47-9c0e-e8ca-2bc1-cb741bc45a1b@collabora.com> (raw)
In-Reply-To: <20230610235016.438460-1-mirsad.todorovac@alu.unizg.hr>

The fix has already been picked up by Andew in mm unstable:

https://lore.kernel.org/all/20230607023727.0E011C433D2@smtp.kernel.org

On 6/11/23 4:50 AM, Mirsad Todorovac wrote:
> GCC 11.3.0 issued warnings about macros and types of arguments [edited]:
> 
> gcc -Wall -I ../tools/testing/selftests/../../.. \
> 	-I ../tools/testing/selftests/../../../tools/include/uapi \
> 	-isystem ../usr/include -no-pie uffd-unit-tests.c vm_util.c \
> 	uffd-common.c -lrt -lpthread -o \
> 	../tools/testing/selftests/mm/uffd-unit-tests
> uffd-unit-tests.c: In function ‘main’:
> uffd-unit-tests.c:1198:41: warning: format not a string literal and no \
> 	format arguments [-Wformat-security]
>  1198 |                         uffd_test_start(test_name);
>       |                                         ^~~~~~~~~
> uffd-unit-tests.c:100:24: note: in definition of macro ‘uffd_test_start’
>   100 |                 printf(__VA_ARGS__);            \
>       |                        ^~~~~~~~~~~
> uffd-unit-tests.c:1205:33: warning: format not a string literal and no \
> 	format arguments [-Wformat-security]
>  1205 |                                 uffd_test_skip(errmsg);
>       |                                 ^~~~~~~~~~~~~~
> 
> The macros are defined as:
> 
>  #define  uffd_test_start(...)  do {             \
>                 printf("Testing ");             \
>                 printf(__VA_ARGS__);            \
>                 printf("... ");                 \
>                 fflush(stdout);                 \
>         } while (0)
> 
>  #define  uffd_test_skip(...)  do {              \
>                 printf("skipped [reason: ");    \
>                 printf(__VA_ARGS__);            \
>                 printf("]\n");                  \
>                 ksft_inc_xskip_cnt();           \
>         } while (0)
> 
> Minor workaround, adding "%s" first argument to macro expansion calls seems
> to be the easiest way to eliminate the warnings.
> 
> Cc: Peter Xu <peterx@redhat.com>
> Cc: linux-mm@kvack.org
> Cc: linux-kselftest@vger.kernel.org
> Fixes: 43759d44dc34 ("selftests/mm: add uffdio register ioctls test")
> Fixes: 16a45b57cbf2 ("selftests/mm: add framework for uffd-unit-test")
> Signed-off-by: Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>
> ---
>  tools/testing/selftests/mm/uffd-unit-tests.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/testing/selftests/mm/uffd-unit-tests.c b/tools/testing/selftests/mm/uffd-unit-tests.c
> index 269c86768a02..d356dd271c84 100644
> --- a/tools/testing/selftests/mm/uffd-unit-tests.c
> +++ b/tools/testing/selftests/mm/uffd-unit-tests.c
> @@ -1195,14 +1195,14 @@ int main(int argc, char *argv[])
>  			snprintf(test_name, sizeof(test_name),
>  				 "%s on %s", test->name, mem_type->name);
>  
> -			uffd_test_start(test_name);
> +			uffd_test_start("%s", test_name);
>  			if (!uffd_feature_supported(test)) {
>  				uffd_test_skip("feature missing");
>  				continue;
>  			}
>  			if (uffd_setup_environment(&args, test, mem_type,
>  						   &errmsg)) {
> -				uffd_test_skip(errmsg);
> +				uffd_test_skip("%s", errmsg);
>  				continue;
>  			}
>  			test->uffd_fn(&args);

-- 
BR,
Muhammad Usama Anjum


  reply	other threads:[~2023-06-11 12:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-10 23:50 Mirsad Todorovac
2023-06-11 12:30 ` Muhammad Usama Anjum [this message]
2023-06-12  0:11   ` Mirsad Goran Todorovac
2023-06-12  7:42     ` Muhammad Usama Anjum

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=109d9c47-9c0e-e8ca-2bc1-cb741bc45a1b@collabora.com \
    --to=usama.anjum@collabora.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mirsad.todorovac@alu.unizg.hr \
    --cc=peterx@redhat.com \
    --cc=shuah@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