From: Anand Jain <anand.jain@oracle.com>
To: Zorro Lang <zlang@redhat.com>
Cc: zlang@kernel.org, fstests@vger.kernel.org,
Linux BTRFS Development <linux-btrfs@vger.kernel.org>
Subject: Re: [GIT PULL] fstests: btrfs changes for for-next v2023.09.03
Date: Mon, 18 Sep 2023 15:07:21 +0800 [thread overview]
Message-ID: <23d3d640-96af-0a57-5b55-a04437cfe2d0@oracle.com> (raw)
In-Reply-To: <20230918050838.k4uwskcplrxaljc4@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
> [1]
> 5bc43d67 (HEAD -> rh-for-next, redhat/rh-for-next) btrfs: add missing commit ids for a few tests using _fixed_by_kernel_commit
> 38b7cb72 btrfs/076: use _fixed_by_kernel_commit to tell the fixing kernel commit
> 6540ed24 btrfs/076: support smaller extent size limit
> 49abf950 fstests: btrfs add more tests into the scrub group
> 7ae7bcb1 common/rc: make _get_max_file_size find file size on mount point
> 0e2055b4 tools/mvtest: ensure testcase is executable (755)
> 39551b4d fstests: btrfs/185 update for single device pseudo device-scan
> 253f54c0 overlay: add test for persistent unique fsid
> 04bbac00 xfs/270: actually test log recovery with unknown rocompat features
> 75adb8f7 xfs/270: actually test file readability
> 8abf8a20 fstests: btrfs/261 fix failure if /var/lib/btrfs isn't writable
> 2da0d269 fstests: use btrfs check repair for repairing btrfs filesystems
>
The btrfs patches in the list looks complete to me for now. Thanks.
> [2]
> [PATCH] generic: test new directory entries are returned after rewinding directory
> [PATCH 0/5] btrfs: simple quotas fstests
> [RFC PATCH v3 0/9] fstests: add btrfs encryption testing
Yeah, I'm planning to have them for the local tests. So I'll take care
of them.
Also, I've included "[PATCH v3] btrfs: Add a test for the temp-fsid
feature."
Thanks. Anand
prev parent reply other threads:[~2023-09-18 7:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 14:16 [GIT PULL] fstests: btrfs changes for for-next v2023.09.03 Anand Jain
2023-09-18 5:08 ` Zorro Lang
2023-09-18 7:07 ` Anand Jain [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=23d3d640-96af-0a57-5b55-a04437cfe2d0@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;
as well as URLs for NNTP newsgroup(s).