From: "Darrick J. Wong" <djwong@kernel.org>
To: Brian Foster <bfoster@redhat.com>
Cc: fstests@vger.kernel.org, linux-xfs@vger.kernel.org,
josef@toxicpanda.com, david@fromorbit.com
Subject: Re: [PATCH v2 2/4] fsx: factor out a file size update helper
Date: Wed, 28 Aug 2024 18:28:28 -0700 [thread overview]
Message-ID: <20240829012828.GG6224@frogsfrogsfrogs> (raw)
In-Reply-To: <20240828181534.41054-3-bfoster@redhat.com>
On Wed, Aug 28, 2024 at 02:15:32PM -0400, Brian Foster wrote:
> In preparation for support for eof page pollution, factor out a file
> size update helper. This updates the internally tracked file size
> based on the upcoming operation and zeroes the appropriate range in
> the good buffer for extending operations.
>
> Signed-off-by: Brian Foster <bfoster@redhat.com>
Looks like a straightforward hoist now.
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> ltp/fsx.c | 49 +++++++++++++++++++++----------------------------
> 1 file changed, 21 insertions(+), 28 deletions(-)
>
> diff --git a/ltp/fsx.c b/ltp/fsx.c
> index c5727cff..4a9be0e1 100644
> --- a/ltp/fsx.c
> +++ b/ltp/fsx.c
> @@ -983,6 +983,17 @@ gendata(char *original_buf, char *good_buf, unsigned offset, unsigned size)
> }
> }
>
> +/*
> + * Helper to update the tracked file size. If the offset begins beyond current
> + * EOF, zero the range from EOF to offset in the good buffer.
> + */
> +void
> +update_file_size(unsigned offset, unsigned size)
> +{
> + if (offset > file_size)
> + memset(good_buf + file_size, '\0', offset - file_size);
> + file_size = offset + size;
> +}
>
> void
> dowrite(unsigned offset, unsigned size)
> @@ -1003,10 +1014,8 @@ dowrite(unsigned offset, unsigned size)
> log4(OP_WRITE, offset, size, FL_NONE);
>
> gendata(original_buf, good_buf, offset, size);
> - if (file_size < offset + size) {
> - if (file_size < offset)
> - memset(good_buf + file_size, '\0', offset - file_size);
> - file_size = offset + size;
> + if (offset + size > file_size) {
> + update_file_size(offset, size);
> if (lite) {
> warn("Lite file size bug in fsx!");
> report_failure(149);
> @@ -1070,10 +1079,8 @@ domapwrite(unsigned offset, unsigned size)
> log4(OP_MAPWRITE, offset, size, FL_NONE);
>
> gendata(original_buf, good_buf, offset, size);
> - if (file_size < offset + size) {
> - if (file_size < offset)
> - memset(good_buf + file_size, '\0', offset - file_size);
> - file_size = offset + size;
> + if (offset + size > file_size) {
> + update_file_size(offset, size);
> if (lite) {
> warn("Lite file size bug in fsx!");
> report_failure(200);
> @@ -1136,9 +1143,7 @@ dotruncate(unsigned size)
>
> log4(OP_TRUNCATE, 0, size, FL_NONE);
>
> - if (size > file_size)
> - memset(good_buf + file_size, '\0', size - file_size);
> - file_size = size;
> + update_file_size(size, 0);
>
> if (testcalls <= simulatedopcount)
> return;
> @@ -1247,16 +1252,8 @@ do_zero_range(unsigned offset, unsigned length, int keep_size)
> log4(OP_ZERO_RANGE, offset, length,
> keep_size ? FL_KEEP_SIZE : FL_NONE);
>
> - if (!keep_size && end_offset > file_size) {
> - /*
> - * If there's a gap between the old file size and the offset of
> - * the zero range operation, fill the gap with zeroes.
> - */
> - if (offset > file_size)
> - memset(good_buf + file_size, '\0', offset - file_size);
> -
> - file_size = end_offset;
> - }
> + if (!keep_size && end_offset > file_size)
> + update_file_size(offset, length);
>
> if (testcalls <= simulatedopcount)
> return;
> @@ -1538,10 +1535,8 @@ do_clone_range(unsigned offset, unsigned length, unsigned dest)
>
> log5(OP_CLONE_RANGE, offset, length, dest, FL_NONE);
>
> - if (dest > file_size)
> - memset(good_buf + file_size, '\0', dest - file_size);
> if (dest + length > file_size)
> - file_size = dest + length;
> + update_file_size(dest, length);
>
> if (testcalls <= simulatedopcount)
> return;
> @@ -1757,10 +1752,8 @@ do_copy_range(unsigned offset, unsigned length, unsigned dest)
>
> log5(OP_COPY_RANGE, offset, length, dest, FL_NONE);
>
> - if (dest > file_size)
> - memset(good_buf + file_size, '\0', dest - file_size);
> if (dest + length > file_size)
> - file_size = dest + length;
> + update_file_size(dest, length);
>
> if (testcalls <= simulatedopcount)
> return;
> @@ -1848,7 +1841,7 @@ do_preallocate(unsigned offset, unsigned length, int keep_size)
>
> if (end_offset > file_size) {
> memset(good_buf + file_size, '\0', end_offset - file_size);
> - file_size = end_offset;
> + update_file_size(offset, length);
> }
>
> if (testcalls <= simulatedopcount)
> --
> 2.45.0
>
>
next prev parent reply other threads:[~2024-08-29 1:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 18:15 [PATCH v2 0/4] fstests/fsx: test coverage for eof zeroing Brian Foster
2024-08-28 18:15 ` [PATCH v2 1/4] fsx: don't skip file size and buf updates on simulated ops Brian Foster
2024-08-29 1:27 ` Darrick J. Wong
2024-08-29 14:56 ` Brian Foster
2024-08-28 18:15 ` [PATCH v2 2/4] fsx: factor out a file size update helper Brian Foster
2024-08-29 1:28 ` Darrick J. Wong [this message]
2024-08-28 18:15 ` [PATCH v2 3/4] fsx: support eof page pollution for eof zeroing test coverage Brian Foster
2024-08-29 1:35 ` Darrick J. Wong
2024-08-28 18:15 ` [PATCH v2 4/4] generic: test to run fsx eof pollution Brian Foster
2024-08-29 1:37 ` Darrick J. Wong
2024-09-02 20:11 ` [PATCH v2 0/4] fstests/fsx: test coverage for eof zeroing 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=20240829012828.GG6224@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=bfoster@redhat.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-xfs@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