All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Reichl <preichl@redhat.com>
To: fstests@vger.kernel.org
Subject: [PATCH v2 0/1] generic: test i_blocks for truncated large files
Date: Tue, 13 Sep 2022 14:58:00 +0200	[thread overview]
Message-ID: <20220913125801.56366-1-preichl@redhat.com> (raw)

thanks for the comments on version #1 and sorry for a late reply
- I was on a vacation.

I updated the test as suggested and worked around the EXT2 fail using 
"_within_tolerance" and 1% as the tolerance...I have a mixed feelings
about this - it's not supported by any math, just a magic number to
avoid false positive. Any thoughts?

Thanks!


Pavel Reichl (1):
  generic: test i_blocks for truncated large files

 tests/generic/698     | 48 +++++++++++++++++++++++++++++++++++++++++++
 tests/generic/698.out |  2 ++
 2 files changed, 50 insertions(+)
 create mode 100755 tests/generic/698
 create mode 100644 tests/generic/698.out

-- 
2.37.3


             reply	other threads:[~2022-09-13 12:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 12:58 Pavel Reichl [this message]
2022-09-13 12:58 ` [PATCH v2 1/1] generic: test i_blocks for truncated large files Pavel Reichl
2022-09-14  6:06   ` Zorro Lang
2022-09-14 17:59   ` Darrick J. Wong
2022-09-15  4:07     ` 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=20220913125801.56366-1-preichl@redhat.com \
    --to=preichl@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 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.