All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Kees Cook <kees@kernel.org>
Cc: Amer Al Shanawany <amer.shanawany@gmail.com>,
	Andy Lutomirski <luto@amacapital.net>,
	Will Drewry <wad@chromium.org>, Shuah Khan <shuah@kernel.org>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	Javier Carrasco <javier.carrasco.cruz@gmail.com>,
	kernel test robot <lkp@intel.com>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2] selftests: seccomp: fix format-zero-length warnings
Date: Tue, 11 Jun 2024 08:46:39 -0600	[thread overview]
Message-ID: <43e24489-a3af-4e53-afc6-ff1dd9462ee2@linuxfoundation.org> (raw)
In-Reply-To: <202406100957.750569FFD1@keescook>

On 6/10/24 10:59, Kees Cook wrote:
> On Fri, Jun 07, 2024 at 02:58:47PM -0600, Shuah Khan wrote:
>> On 6/7/24 06:41, Amer Al Shanawany wrote:
>>> fix the following errors by removing empty print statements:
>>> seccomp_benchmark.c:197:24: warning: zero-length gnu_printf format
>>>    string [-Wformat-zero-length]
>>>     197 |         ksft_print_msg("");
>>>         |                        ^~
>>> seccomp_benchmark.c:202:24: warning: zero-length gnu_printf format
>>>    string [-Wformat-zero-length]
>>>     202 |         ksft_print_msg("");
>>>         |                        ^~
>>> seccomp_benchmark.c:204:24: warning: zero-length gnu_printf format
>>>    string [-Wformat-zero-length]
>>>     204 |         ksft_print_msg("");
>>>         |                        ^~
>>>
>>> Reported-by: kernel test robot <lkp@intel.com>
>>> Closes: https://lore.kernel.org/oe-kbuild-all/202312260235.Uj5ug8K9-lkp@intel.com/
>>> Signed-off-by: Amer Al Shanawany <amer.shanawany@gmail.com>
>>> ---
>>> Changes v1 -> v2:
>>> removed empty print statements
>>
>> Kees,
>>
>> Is this change okay with you. I didn't see any use for
>> these empty ksft_print_msg().
>>
>> I will take this patch if you are okay with the change.
> 
> Dropping these means that the "#" marks go missing. Currently:
> 
> # Running on:
> # Linux proton 6.5.0-25-generic #25~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Feb 20 16:09:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
> 
> with the proposed patch:
> 
> # Running on:
> Linux proton 6.5.0-25-generic #25~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Feb 20 16:09:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
> 
> This breaks the TAP syntax for the test, so we should find a different
> solution.
> 
> Perhaps:
> 
> ksft_print_msg("%s", "");
> 
> ?
> 

Thank you Kees. Yes that would work.

Amer, please send me v3 based on Kees's suggestions.

thanks,
-- Shuah


  reply	other threads:[~2024-06-11 14:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 11:54 [PATCH] selftests: seccomp: fix format-zero-length warnings Amer Al Shanawany
2024-06-06 22:41 ` Shuah Khan
2024-06-07 12:41   ` [PATCH v2] " Amer Al Shanawany
2024-06-07 20:58     ` Shuah Khan
2024-06-10 16:59       ` Kees Cook
2024-06-11 14:46         ` Shuah Khan [this message]
2024-06-11 15:16           ` [PATCH v3] " Amer Al Shanawany
2024-06-12 18:44             ` Kees Cook

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=43e24489-a3af-4e53-afc6-ff1dd9462ee2@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=amer.shanawany@gmail.com \
    --cc=javier.carrasco.cruz@gmail.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=luto@amacapital.net \
    --cc=shuah@kernel.org \
    --cc=wad@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.