From: Joanne Koong <joannelkoong@gmail.com>
To: fstests@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, bfoster@redhat.com,
djwong@kernel.org, nirjhar@linux.ibm.com, zlang@redhat.com,
kernel-team@meta.com
Subject: [PATCH v5 0/2] fstests: test reads/writes from hugepages-backed buffers
Date: Tue, 21 Jan 2025 13:56:39 -0800 [thread overview]
Message-ID: <20250121215641.1764359-1-joannelkoong@gmail.com> (raw)
There was a recent bug in rc1 [1] that was due to faulty handling for
userspace buffers backed by hugepages.
This patchset adds generic tests for reads/writes from buffers backed by
hugepages.
[1] https://lore.kernel.org/linux-fsdevel/p3iss6hssbvtdutnwmuddvdadubrhfkdoosgmbewvo674f7f3y@cwnwffjqltzw/
Changelog:
v4:
https://lore.kernel.org/linux-fsdevel/20250118004759.2772065-1-joannelkoong@gmail.com/
- Fix identationand and if logic structure for collapses (Darrick)
v3:
https://lore.kernel.org/linux-fsdevel/20250115183107.3124743-1-joannelkoong@gmail.com/
- Gate '-h' text behind MADVISE_COLLAPSE (Darrick)
- Add periodic hugepages collapsing for memory constrained environments (Darrick)
- Use tabs instead of spaces (Darrick)
- Refactor #ifdef MADVISE_COLLAPSE placements
v2:
https://lore.kernel.org/linux-fsdevel/20241227193311.1799626-1-joannelkoong@gmail.com/
- Gate -h and MADV_COLLAPSE usage to get it compatible on old systems (Zorro)
- Use calloc instead of malloc/memset (Nirjhar)
- Update exit codes in 1st patch
- Add Brian's reviewed-bys
v1:
https://lore.kernel.org/linux-fsdevel/20241218210122.3809198-1-joannelkoong@gmail.com/
- Refactor out buffer initialization (Brian)
- Update commit messages of 1st patch (Brian)
- Use << 10 instead of * 1024 (Nirjhar)
- Replace CONFIG_TRANSPARENT_HUGEPAGE check with checking
'sys/kernel/mm/transparent_hugepage/' (Darrick)
- Integrate readbdy and writebdy options
- Update options of generic/759 to include psize/bsize
Joanne Koong (2):
fsx: support reads/writes from buffers backed by hugepages
generic: add tests for read/writes from hugepages-backed buffers
common/rc | 13 ++++
ltp/fsx.c | 166 ++++++++++++++++++++++++++++++++++++++----
tests/generic/758 | 22 ++++++
tests/generic/758.out | 4 +
tests/generic/759 | 26 +++++++
tests/generic/759.out | 4 +
6 files changed, 222 insertions(+), 13 deletions(-)
create mode 100755 tests/generic/758
create mode 100644 tests/generic/758.out
create mode 100755 tests/generic/759
create mode 100644 tests/generic/759.out
--
2.47.1
next reply other threads:[~2025-01-21 21:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 21:56 Joanne Koong [this message]
2025-01-21 21:56 ` [PATCH v5 1/2] fsx: support reads/writes from buffers backed by hugepages Joanne Koong
2025-02-02 14:25 ` Zorro Lang
2025-02-03 18:04 ` Joanne Koong
2025-02-03 18:59 ` Darrick J. Wong
2025-02-03 19:23 ` Joanne Koong
2025-02-03 19:41 ` Darrick J. Wong
2025-02-03 19:57 ` Joanne Koong
2025-02-03 20:01 ` Darrick J. Wong
2025-02-03 21:40 ` Joanne Koong
2025-02-03 21:54 ` Darrick J. Wong
2025-02-04 4:21 ` Darrick J. Wong
2025-02-04 20:50 ` Joanne Koong
2025-02-04 21:31 ` Darrick J. Wong
2025-02-04 21:52 ` Joanne Koong
2025-02-04 17:05 ` Zorro Lang
2025-02-04 20:54 ` Joanne Koong
2025-01-21 21:56 ` [PATCH v5 2/2] generic: add tests for read/writes from hugepages-backed buffers Joanne Koong
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=20250121215641.1764359-1-joannelkoong@gmail.com \
--to=joannelkoong@gmail.com \
--cc=bfoster@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=kernel-team@meta.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nirjhar@linux.ibm.com \
--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