From: Ritesh Harjani <riteshh@linux.ibm.com>
To: fstests@vger.kernel.org
Cc: guan@eryu.me, linux-ext4@vger.kernel.org,
anju@linux.vnet.ibm.com, Ritesh Harjani <riteshh@linux.ibm.com>
Subject: [PATCH 0/2] Section handling patch and huge sparse file generic/618
Date: Fri, 4 Dec 2020 16:13:52 +0530 [thread overview]
Message-ID: <cover.1607078368.git.riteshh@linux.ibm.com> (raw)
Patch-1 was suggested from Eryu. This does fixes the multiple section handling
issue which was discussed here [1]. Hence sending it for review and
inclusion in fstests.
Patch-2 - addressed the review comments from [2] w.r.t. ext4 MKFS_OPTIONS
for bs < 4k.
[1]: https://patchwork.kernel.org/project/fstests/cover/cover.1604000570.git.riteshh@linux.ibm.com/
[2]: https://patchwork.kernel.org/patch/11864921
Eryu Guan (1):
check: source common/rc again if TEST_DEV was recreated
Ritesh Harjani (1):
generic: Add test to check for mounting a huge sparse dm device
check | 4 +++
common/rc | 10 +++++++
tests/generic/618 | 70 +++++++++++++++++++++++++++++++++++++++++++
tests/generic/618.out | 3 ++
tests/generic/group | 1 +
5 files changed, 88 insertions(+)
create mode 100755 tests/generic/618
create mode 100644 tests/generic/618.out
--
2.26.2
next reply other threads:[~2020-12-04 10:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 10:43 Ritesh Harjani [this message]
2020-12-04 10:43 ` [PATCH 1/2] check: source common/rc again if TEST_DEV was recreated Ritesh Harjani
2020-12-04 10:43 ` [PATCH 2/2] generic: Add test to check for mounting a huge sparse dm device Ritesh Harjani
2020-12-06 13:50 ` Eryu Guan
2020-12-06 14:14 ` Eryu Guan
2020-12-07 8:37 ` Ritesh Harjani
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=cover.1607078368.git.riteshh@linux.ibm.com \
--to=riteshh@linux.ibm.com \
--cc=anju@linux.vnet.ibm.com \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=linux-ext4@vger.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 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.