public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Krister Johansen <kjlx@templeofstupid.com>
To: Chandan Babu R <chandan.babu@oracle.com>,
	"Darrick J. Wong" <djwong@kernel.org>,
	Dave Chinner <david@fromorbit.com>
Cc: Dave Chinner <dchinner@redhat.com>, Zorro Lang <zlang@kernel.org>,
	linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [RFC PATCH 0/2] xfstests: fstests for agfl reservation
Date: Thu, 15 Aug 2024 12:36:50 -0700	[thread overview]
Message-ID: <cover.1723690703.git.kjlx@templeofstupid.com> (raw)
In-Reply-To: <cover.1723687224.git.kjlx@templeofstupid.com>

Hi,
This set includes a test to trigger the xfs_bmap_extents_to_btree WARN
that tends to the the most observed symptom of the dependent allocation
failures that this author encounters.  The patches to fix the problem
also introduced a failure in xfs/306.  I'm including a fix for that as
well, though if this is an inappropriate resolution of the underlying
problem, I'm happy to take another approach.

This is sent as an RFC since it's my first foray into submitting
xfstests.  The 608 test should be deterministic on kernels that precede
the AG-aware allocator re-write.  On my machines on recent kernels I'm
getting about a 40-50% success rate with triggering the bug with this
test now.

-K

Krister Johansen (2):
  xfs/608: a test case for xfs_bmap_extents_to_btree allocation failure
  xfs/306: update resblks to account for increased per-ag reservation
    size

 tests/xfs/306     |   2 +-
 tests/xfs/608     | 372 ++++++++++++++++++++++++++++++++++++++++++++++
 tests/xfs/608.out |   2 +
 3 files changed, 375 insertions(+), 1 deletion(-)
 create mode 100755 tests/xfs/608
 create mode 100644 tests/xfs/608.out


base-commit: f5ada754d5838d29fd270257003d0d123a9d1cd2
-- 
2.25.1


  parent reply	other threads:[~2024-08-15 19:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15 19:29 [PATCHSET] AGFL reservation changes Krister Johansen
2024-08-15 19:30 ` [PATCH 0/5] linux: Modifying per-ag reservation to account for dependent allocations Krister Johansen
2024-08-15 19:31   ` [PATCH 1/5] xfs: count the number of blocks in a per-ag reservation Krister Johansen
2024-08-15 19:32   ` [PATCH 2/5] xfs: move calculation in xfs_alloc_min_freelist to its own function Krister Johansen
2024-08-15 19:33   ` [PATCH 3/5] xfs: make alloc_set_aside and friends aware of per-AG reservations Krister Johansen
2024-08-15 19:34   ` [PATCH 4/5] xfs: push the agfl set aside into xfs_alloc_space_available Krister Johansen
2024-08-15 19:35   ` [PATCH 5/5] xfs: include min freelist in m_ag_max_usable Krister Johansen
2024-08-15 19:36 ` Krister Johansen [this message]
2024-08-15 19:37   ` [RFC PATCH 1/2] xfs/608: a test case for xfs_bmap_extents_to_btree allocation failure Krister Johansen
2024-08-15 19:40   ` [RFC PATCH 2/2] xfs/306: update resblks to account for increased per-ag reservation size Krister Johansen

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=cover.1723690703.git.kjlx@templeofstupid.com \
    --to=kjlx@templeofstupid.com \
    --cc=chandan.babu@oracle.com \
    --cc=david@fromorbit.com \
    --cc=dchinner@redhat.com \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=zlang@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