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.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEUzaAxoMeQq6m2jMV+H93GTRKtOsFAmEelYMACgkQ+H93GTRK
tOuavA//TLT9QIFDFOVRz52BwR8azmNinsMy/ZtLTVjrWOEugn+/yfRX/X+hqbmO
h/BGF250nPI7cQxtsTwOyjaV/FDlbDb0sSmPnfd/XM3gSfmHxwQGLf6ksMgFHgKL
aUi7BXa8XX3rSLY19o31GWC7x4WVaq+TV1LY7PASCVuxUa+wtAo7rPwJORJBPtST
cY7UAe4lBwcKQt4lg1F/+W2aEQ9HtZT6t+tu30q6NBEBkrEdEFH91096eKTjJCaM
ZKi4Mxj0mSk1+uZ9o2kbkWiDfFxJDiBHhBXJTssT+bF4SilEfsNZwf13hwt8gPE5
SixMfYpUJXfjzO59JYdykpBuPEHG6GWm2KDt6BGE0LYNPiZvlfpPHCnHWRdfLbq9
KWryO90Z9S7R5XBzqW9VfGtpMMZJINGwI1Cr8cYLW2skN9I7CHcR20Dua65HVs/3
6ZNFK1/KqSbKpmkecCuaXlakk46K+tb/jWueS+z2/l2fK+7rudbizzlu8eqVN9L6
pQf+hcuiGA8v7mRDp4ppFXTjIFsaDLTRB3/CXSaRg384aF+GUWJPrHLQIuXEopdt
g9NrmPzqFpZi9l87OtxDzkLBMWrLBx+GL8qSKZUTl8o3Ua2YUga5suJisLxXiJt2
XA+R3dXlfLh8zsTFKkjs4Cm1k9sOYEWtSqqIm30rSd2id9GraAk=
=5MRR
-----END PGP SIGNATURE-----