tag name | xfs-5.15-merge-5 (19f97cc06d05eab4242aa1a4db4e584e21fc9d27) |
tag date | 2021-08-21 13:15:09 -0700 |
tagged by | Darrick J. Wong <djwong@kernel.org> |
tagged object | commit 61e0d0cc51... |
New code for 5.15:
- Fix a potential log livelock on busy filesystems when there's so much
work going on that we can't finish a quotaoff before filling up the log
by removing the ability to disable quota accounting.
- Introduce the ability to use per-CPU data structures in XFS so that
we can do a better job of maintaining CPU locality for certain
operations.
- Defer inode inactivation work to per-CPU lists, which will help us
batch that processing. Deletions of large sparse files will *appear*
to run faster, but all that means is that we've moved the work to the
backend.
- Drop the EXPERIMENTAL warnings from the y2038+ support and the inode
btree counters, since it's been nearly a year and no complaints have
come in.
- Remove more of our bespoke kmem* variants in favor of using the
standard Linux calls.
- Prepare for the addition of log incompat features in upcoming cycles
by actually adding code to support this.
- Small cleanups of the xattr code in preparation for landing support
for full logging of extended attribute updates in a future cycle.
- Replace the various log shutdown state and flag code all over xfs
with a single atomic bit flag.
- Fix a serious log recovery bug where log item replay can be skipped
based on the start lsn of a transaction even though the transaction
commit lsn is the key data point for that by enforcing start lsns to
appear in the log in the same order as commit lsns.
- Enable pipelining in the code that pushes log items to disk.
- Drop ->writepage.
- Fix some bugs in GETFSMAP where the last fsmap record reported for a
device could extend beyond the end of the device, and a separate bug
where query keys for one device could be applied to another.
- Don't let GETFSMAP query functions edit their input parameters.
- Small cleanups to the scrub code's handling of perag structures.
- Small cleanups to the incore inode tree walk code.
- Constify btree function parameters that aren't changed, so that there
will never again be confusion about range query functions changing
their input parameters.
- Standardize the format and names of tracepoint data attributes.
- Clean up all the mount state and feature flags to use wrapped bitset
functions instead of inconsistently open-coded flag checks.
- Fix some confusion between xfs_buf hash table key variable vs. block
number.
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEUzaAxoMeQq6m2jMV+H93GTRKtOsFAmEhX4MACgkQ+H93GTRK
tOtTQQ/9Gwy7FiHUk0vsC8nIsxKMzfND8gwKkwdz762WdWLUXr0dFqe/jE87j4GZ
d7BUTTwy3q5uzXhV2hica4ngY5kwj/sgQ0YvhgQUlkTtrCYDM6lapTzirOhuONsA
vPG0zg67lT2M3UygMqo9GfOiksXWVOcuzYUYwz504ogbORSd98sNjTaEt+WBfCiJ
VSiZ6disV3haeHCO2ZkVDiPx9GBDuWEqSgCNYX2C1dhFOUIFOVbCDAwfBkhVUnzJ
4YGi8j5+71GlsfSme8u6WOX9npLxdEjDQnOZa84WjrEWfospnj6O1XrZ5JEFZyfd
KLNKk9EKttQTqlMcKAs0UIsV/DW2vgA7WDZrHbBDoYzircIUbkgftTqphZB9Bken
//er8KE8Q+euLHVu3agEs4lIAcXcOqxyE2kdBekAK8QztO9TttXKpfK845Pvtb2F
bhbsbv685mNlZNI7J8YDJLA/p0EGxTKXAI1ADe9QHa8WpPKP8G731HxDzaNaRqaE
f4xR5sdq/GtkReRkAqkAwFiPytMwNJwq1y9UKwXudTtsxZlah2GHo+ZJt0DR28YD
Gy0j3DuoqLmjwOlhFjGcM8ld7ldwvzJS6LAzHFK9cdCX7D/kkUid3CXLpIKt9u+g
4xlZASy/s75C04LMcx+Onil4Tbyzo2hRKSDGpyfA8sUqVyTCdCk=
=/wxh
-----END PGP SIGNATURE-----