public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Shivam Chaudhary <cvam0000@gmail.com>, shuah@kernel.org
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v5 0/2] kselftest: tmpfs: Add ksft macros and skip if no root
Date: Tue, 3 Dec 2024 14:50:17 -0700	[thread overview]
Message-ID: <35238cbe-7f4e-4486-915e-ab13ca0120de@linuxfoundation.org> (raw)
In-Reply-To: <20241112143056.565122-1-cvam0000@gmail.com>

On 11/12/24 07:30, Shivam Chaudhary wrote:
> This version 5 patch series replace direct error handling methods with ksft
> macros, which provide better reporting.Currently, when the tmpfs test runs,
> it does not display any output if it passes,and if it fails
> (particularly when not run as root),it simply exits without any warning or
> message.
> 
> This series of patch adds:
> 
> 1. Add 'ksft_print_header()' and 'ksft_set_plan()'
>     to structure test outputs more effectively.
> 
> 2. Error if not run as root.

This should be a skip - not a fail.

> 
> 3. Replace direct error handling with 'ksft_test_result_*',
>     'ksft_exit_fail_msg' macros for better reporting.


> 
> v4->v5:
>           - Remove unnecessary pass messages.
>           - Remove unnecessary use of KSFT_SKIP.
>           - Add appropriate use of ksft_exit_fail_msg.
> 
> v4 1/2: https://lore.kernel.org/all/20241105202639.1977356-2-cvam0000@gmail.com/
> v4 2/2: https://lore.kernel.org/all/20241105202639.1977356-3-cvam0000@gmail.com/
> 
> v3->v4:
>           - Start a patchset
>           - Split patch into smaller patches to make it easy to review.
>    Patch1 Replace  'ksft_test_result_skip' with 'KSFT_SKIP' during root run check.
>    Patch2 Replace  'ksft_test_result_fail' with 'KSFT_SKIP' where fail does not make sense,
>           or failure could be due to not unsupported APIs with appropriate warnings.
> 
> 
> v3: https://lore.kernel.org/all/20241028185756.111832-1-cvam0000@gmail.com/
> 
> v2->v3:
>          - Remove extra ksft_set_plan()
>          - Remove function for unshare()
>          - Fix the comment style
> v2: https://lore.kernel.org/all/20241026191621.2860376-1-cvam0000@gmail.com/
> 
> v1->v2:
>          - Make the commit message more clear.
> v1: https://lore.kernel.org/all/20241024200228.1075840-1-cvam0000@gmail.com/T/#u
> 
> 
> thanks
> Shivam
> 
> Shivam Chaudhary (2):
>    selftests: tmpfs: Add Test-fail if not run as root
>    selftests: tmpfs: Add kselftest support to tmpfs
> 
>   .../selftests/tmpfs/bug-link-o-tmpfile.c      | 60 ++++++++++++-------
>   1 file changed, 37 insertions(+), 23 deletions(-)
> 

thanks,
-- Shuah

      parent reply	other threads:[~2024-12-03 21:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 14:30 [PATCH v5 0/2] kselftest: tmpfs: Add ksft macros and skip if no root Shivam Chaudhary
2024-11-12 14:30 ` [PATCH v5 1/2] selftests: tmpfs: Add Test-fail if not run as root Shivam Chaudhary
2024-12-03 21:50   ` Shuah Khan
2024-11-12 14:30 ` [PATCH v5 2/2] selftests: tmpfs: Add kselftest support to tmpfs Shivam Chaudhary
2024-12-03 21:51   ` Shuah Khan
2024-12-03 21:50 ` 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=35238cbe-7f4e-4486-915e-ab13ca0120de@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=cvam0000@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --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