FS/XFS testing framework
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: fstests@vger.kernel.org
Subject: [PATCH 0/2] fsx: support unshare range fallocate mode
Date: Thu, 26 Sep 2024 10:41:45 -0400	[thread overview]
Message-ID: <20240926144147.106685-1-bfoster@redhat.com> (raw)

Hi all,

Here's v1 of unshare range mode support for fsx. This includes only
minor tweaks from the RFC version and I tacked on a second patch to try
and fix up some missing fallocate flag ifdefs. Note again this applies
on top of the eof pollution mode series currently pending in the
upstream repo. Thoughts, reviews, flames appreciated.

Brian

v1:
- Minor cleanups, add ifdefs.
- Added patch to fix up missing fallocate flag ifdefs.
rfc: https://lore.kernel.org/fstests/20240906185606.136402-1-bfoster@redhat.com/

Brian Foster (2):
  fsx: support unshare range fallocate mode
  fsx: add missing fallocate flag ifdefs

 ltp/fsx.c | 122 +++++++++++++++++++++++++++++++++++++++++-------------
 1 file changed, 94 insertions(+), 28 deletions(-)

-- 
2.46.1


             reply	other threads:[~2024-09-26 14:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26 14:41 Brian Foster [this message]
2024-09-26 14:41 ` [PATCH 1/2] fsx: support unshare range fallocate mode Brian Foster
2024-09-26 14:48   ` Darrick J. Wong
2024-09-26 15:53     ` Brian Foster
2024-09-27  3:40       ` Zorro Lang
2024-09-26 14:41 ` [PATCH 2/2] fsx: add missing fallocate flag ifdefs Brian Foster
2024-09-26 14:50   ` Darrick J. Wong
2024-09-26 15:55     ` Brian Foster
2024-09-27  5:42       ` Zorro Lang
2024-09-27 12:07         ` Brian Foster
2024-09-27 15:25           ` Darrick J. Wong
2024-09-27 18:34             ` Brian Foster
2024-09-28  8:03             ` 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=20240926144147.106685-1-bfoster@redhat.com \
    --to=bfoster@redhat.com \
    --cc=fstests@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox