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: [PATCHSET] AGFL reservation changes
Date: Thu, 15 Aug 2024 12:29:58 -0700 [thread overview]
Message-ID: <cover.1723687224.git.kjlx@templeofstupid.com> (raw)
Hi,
This patchset contains changes to linux and to xfstests to address a
reoccuring panic in xfs_bmap_extents_to_btree.
The RFC was discussed here:
https://lore.kernel.org/linux-xfs/cover.1718232004.git.kjlx@templeofstupid.com/T/#t
The kernel changes modify how the AGFL reservation is calculated when a
filesystem is mounted. This is also pushed into the in-core per-AG
structures to ensure that they do not consume the additional space
reserved by this change.
Additionally, this includes a pair of xfstest patches. The first
introduces a test that triggers the problem we're trying to fix, as
xfs/608. The second is a modification to xfs/306, which started failing
because the increased space that is reserved by these changes is above
the global reserve limit that this test intentionally lowers. The
second patch increases this limit by one block. If this seems wrong,
I'm happy to debug further. The change was based upon the assumption
that artifically lowered global reservation limits had to be cognizant
of the per-AG limits.
-K
next reply other threads:[~2024-08-15 19:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 19:29 Krister Johansen [this message]
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 ` [RFC PATCH 0/2] xfstests: fstests for agfl reservation Krister Johansen
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.1723687224.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