FS/XFS testing framework
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Zorro Lang <zlang@redhat.com>, Anand Jain <anand.jain@oracle.com>
Cc: fstests@vger.kernel.org, zlang@kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/3] fstests: btrfs/219, add _fixed_by_kernel_commit
Date: Wed, 15 Feb 2023 13:33:30 +0800	[thread overview]
Message-ID: <679cbe50-ef90-0c4e-4b37-d04c64f70c04@oracle.com> (raw)
In-Reply-To: <20230214060702.5jiajtxcogixruqj@zlang-mailbox>

On 2/14/23 14:07, Zorro Lang wrote:
> On Fri, Feb 10, 2023 at 09:41:20PM +0800, Anand Jain wrote:
>> btrfs/219 is in the auto group so add the _fixed_by_kernel_commit
>> tag for the benifit of the older kernels. The required commit is not yet
>> in the mainline so there is no commit id yet.
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---
>>   tests/btrfs/219 | 4 +++-
>>   1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/tests/btrfs/219 b/tests/btrfs/219
>> index 528175b8a4b9..79ba31549268 100755
>> --- a/tests/btrfs/219
>> +++ b/tests/btrfs/219
>> @@ -8,7 +8,7 @@
>>   # to make sure we do not allow stale devices, which can end up with some wonky
>>   # behavior for loop back devices.  This was changed with
>>   #
>> -#   btrfs: allow single disk devices to mount with older generations
>> +#	btrfs: free device in btrfs_close_devices for a single device filesystem
>>   #
>>   # But I've added a few other test cases so it's clear what we expect to happen
>>   # currently.
>> @@ -42,6 +42,8 @@ _supported_fs btrfs
>>   _require_test
>>   _require_loop
>>   _require_btrfs_forget_or_module_loadable
>> +_fixed_by_kernel_commit xxxxxxxxxxxx \
>> +	"btrfs: free device in btrfs_close_devices for a single device filesystem"
> 
> It was just merged ;)
> 
> commit 5f58d783fd7823b2c2d5954d1126e702f94bfc4c
> Author: Anand Jain <anand.jain@oracle.com>
> Date:   Fri Jan 20 21:47:16 2023 +0800
> 
>      btrfs: free device in btrfs_close_devices for a single device filesystem
> 

Ok. I'm updating the commit id.

I am sending v2 just for this path.

Also, I can combine the series into a single patch if you prefer.

Thanks.


> 
>>   
>>   loop_mnt=$TEST_DIR/$seq.mnt
>>   loop_mnt1=$TEST_DIR/$seq.mnt1
>> -- 
>> 2.31.1
>>
> 


  reply	other threads:[~2023-02-15  5:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 13:41 [PATCH 0/3] fstests: btrfs- add _fixed_by for new tests in the auto group Anand Jain
2023-02-10 13:41 ` [PATCH 1/3] fstests: btrfs/198, add _fixed_by_kernel_commit Anand Jain
2023-02-10 13:41 ` [PATCH 2/3] fstests: btrfs/219, " Anand Jain
2023-02-14  6:07   ` Zorro Lang
2023-02-15  5:33     ` Anand Jain [this message]
2023-02-15  5:37   ` [PATCH v2] " Anand Jain
2023-02-10 13:41 ` [PATCH 3/3] fstests: btrfs/185, " Anand Jain
2023-02-15  7:51 ` [PATCH v3] fstests: btrfs/185, 198 and 219 " Anand Jain
2023-02-15 14:24   ` 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=679cbe50-ef90-0c4e-4b37-d04c64f70c04@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=zlang@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