From: "Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>
To: fstests@vger.kernel.org
Cc: ritesh.list@gmail.com, djwong@kernel.org, mcgrof@kernel.org,
gost.dev@samsung.com, zlang@redhat.com, kernel@pankajraghav.com,
Pankaj Raghav <p.raghav@samsung.com>
Subject: [PATCH v3 0/3] more lbs test fixes
Date: Mon, 27 May 2024 13:48:31 +0200 [thread overview]
Message-ID: <20240527114834.167521-1-kernel@pankajraghav.com> (raw)
From: Pankaj Raghav <p.raghav@samsung.com>
These are some of the tests that failed when we were working on LBS
patches [1].
generic/436 and xfs/008 are adapted to work with bs > ps systems.
xfs/161 is an upstream failure, and it happens even on bs <= ps systems.
Changes since v2:
- Addes RVB tags
- Removed pgsize fallback in xfs/008 (Ritesh)
Changes since v1:
- Corrected copy pasta error in generic/436
- xfs/161 removed hardcoded and incorporated ritesh's comments
[1] https://lore.kernel.org/linux-xfs/20240503095353.3798063-1-mcgrof@kernel.org/
Pankaj Raghav (3):
xfs/161: adapt the test case for 64k FS blocksize
generic/436: round up bufsz to nearest filesystem blksz
xfs/008: use block size instead of the pagesize
src/seek_sanity_test.c | 8 ++++----
tests/xfs/008 | 20 +++++++++-----------
tests/xfs/008.out | 8 ++++----
tests/xfs/161 | 16 ++++++++++++----
4 files changed, 29 insertions(+), 23 deletions(-)
base-commit: 9837971383733ad59ead121dcc4b13f89829d389
--
2.34.1
next reply other threads:[~2024-05-27 11:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 11:48 Pankaj Raghav (Samsung) [this message]
2024-05-27 11:48 ` [PATCH v3 1/3] xfs/161: adapt the test case for 64k FS blocksize Pankaj Raghav (Samsung)
2024-05-27 11:48 ` [PATCH v3 2/3] generic/436: round up bufsz to nearest filesystem blksz Pankaj Raghav (Samsung)
2024-05-27 13:01 ` Pankaj Raghav (Samsung)
2024-05-27 13:26 ` Zorro Lang
2024-05-28 9:12 ` Pankaj Raghav (Samsung)
2024-05-27 11:48 ` [PATCH v3 3/3] xfs/008: use block size instead of the pagesize Pankaj Raghav (Samsung)
2024-05-27 17:03 ` 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=20240527114834.167521-1-kernel@pankajraghav.com \
--to=kernel@pankajraghav.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=gost.dev@samsung.com \
--cc=mcgrof@kernel.org \
--cc=p.raghav@samsung.com \
--cc=ritesh.list@gmail.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 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.