public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org, djwong@kernel.org
Subject: Re: [PATCH v6 2/6] fstests: check: fix unset seqres in run_section()
Date: Thu, 10 Apr 2025 05:31:39 +0800	[thread overview]
Message-ID: <9dc6a550-5e4a-4ff1-8961-9d6dd758a83f@oracle.com> (raw)
In-Reply-To: <20250409095725.xumxhw54igwapuue@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>



On 9/4/25 17:57, Zorro Lang wrote:
> On Wed, Apr 09, 2025 at 03:43:14PM +0800, Anand Jain wrote:
>> Ensure seqres is set early in run_section().
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---
>>   check | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/check b/check
>> index 32890470a020..16f695e9d75c 100755
>> --- a/check
>> +++ b/check
>> @@ -804,6 +804,7 @@ function run_section()
>>   
>>   	seq="check.$$"
>>   	check="$RESULT_BASE/check"
>> +	seqres="$check"
> 
> The "seqres" even might be used earlier than that. If your rootfs is readonly,
> you'll see that.
> 

Zorro,

Thanks a lot for the review and RVB!

I’ll take care of this patch 2/6 in a separate patchset.
Meanwhile, could you help merge the rest of the sysfs patches,
except for patch 2/6? I don't want the seqres issue to block
the rest of the sysfs patches.

Thanks, Anand

> Thanks,
> Zorro
> 
>>   
>>   	# don't leave old full output behind on a clean run
>>   	rm -f $check.full
>> @@ -849,7 +850,6 @@ function run_section()
>>   	  fi
>>   	fi
>>   
>> -	seqres="$check"
>>   	_check_test_fs
>>   
>>   	loop_status=()	# track rerun-on-failure state
>> -- 
>> 2.47.0
>>
> 


  reply	other threads:[~2025-04-09 21:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09  7:43 [PATCH v6 0/6] fstests: btrfs: add test case to validate sysfs input arguments Anand Jain
2025-04-09  7:43 ` [PATCH v6 1/6] fstests: common/rc: set_fs_sysfs_attr: redirect errors to stdout Anand Jain
2025-04-09  7:43 ` [PATCH v6 2/6] fstests: check: fix unset seqres in run_section() Anand Jain
2025-04-09  9:57   ` Zorro Lang
2025-04-09 21:31     ` Anand Jain [this message]
2025-04-10  7:12       ` Zorro Lang
2025-05-24  1:39       ` Anand Jain
2025-04-09  7:43 ` [PATCH v6 3/6] fstests: filter: helper for sysfs error filtering Anand Jain
2025-04-09  7:43 ` [PATCH v6 4/6] fstests: common/sysfs: add new file sysfs and helpers Anand Jain
2025-04-09 10:21   ` Zorro Lang
2025-04-09  7:43 ` [PATCH v6 5/6] fstests: btrfs: testcase for sysfs policy syntax verification Anand Jain
2025-04-09 10:22   ` Zorro Lang
2025-04-09  7:43 ` [PATCH v6 6/6] fstests: btrfs: testcase for sysfs chunk_size attribute validation Anand Jain
2025-04-09 10:23   ` Zorro Lang

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=9dc6a550-5e4a-4ff1-8961-9d6dd758a83f@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=zlang@redhat.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