From: Amir Goldstein <amir73il@gmail.com>
To: "Darrick J . Wong" <djwong@kernel.org>
Cc: Leah Rumancik <leah.rumancik@gmail.com>,
Chandan Babu R <chandan.babu@oracle.com>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH 5.10 CANDIDATE 0/7] xfs stable candidate patches for 5.10.y (from v5.18+)
Date: Sun, 28 Aug 2022 15:46:07 +0300 [thread overview]
Message-ID: <20220828124614.2190592-1-amir73il@gmail.com> (raw)
Hi Darrick,
This 5.10.y backport series contains fixes from v5.18 and v5.19 releases.
Patches 1-5 in this series have already been applied to 5.15.y in Leah's
latest update [1], so this 5.10.y is is mostly catching up with 5.15.y.
Patches 2-3 from the last 5.15.y update have not been picked for 5.10.y,
because they were not trivial to backport as the quota code is quite
different betrween 5.10.y and upstream.
This omission leave fstests generic/681,682 broken on 5.10.y.
Patches 6-7 in this 5.10.y update have not been applied to 5.15.y yet.
I pointed Leah's attention to these patches and she said she will
include them in a following 5.15.y update.
In particular, Darrick has pointed me at the fix in patch 6 a long time
ago, but I was waiting to apply fixes to 5.10.y in chronoligal order.
Please note that the upstream fix 6f5097e3367a ("xfs: fix xfs_ifree()
error handling to not leak perag ref") Which Fixes: 9a5280b312e2e
("xfs: reorder iunlink remove operation in xfs_ifree")
is not relevant for the 5.10.y backport.
These patches has gone through the usual 30 auto group runs x 5 configs
on kdevops.
Thanks,
Amir.
[1] https://lore.kernel.org/linux-xfs/20220819181431.4113819-1-leah.rumancik@gmail.com/
Amir Goldstein (1):
xfs: remove infinite loop when reserving free block pool
Brian Foster (1):
xfs: fix soft lockup via spinning in filestream ag selection loop
Darrick J. Wong (2):
xfs: always succeed at setting the reserve pool size
xfs: fix overfilling of reserve pool
Dave Chinner (2):
xfs: reorder iunlink remove operation in xfs_ifree
xfs: validate inode fork size against fork format
Eric Sandeen (1):
xfs: revert "xfs: actually bump warning counts when we send warnings"
fs/xfs/libxfs/xfs_inode_buf.c | 35 +++++++++++++++++------
fs/xfs/xfs_filestream.c | 7 +++--
fs/xfs/xfs_fsops.c | 52 ++++++++++++++---------------------
fs/xfs/xfs_inode.c | 22 ++++++++-------
fs/xfs/xfs_mount.h | 8 ++++++
fs/xfs/xfs_trans_dquot.c | 1 -
6 files changed, 71 insertions(+), 54 deletions(-)
--
2.25.1
next reply other threads:[~2022-08-28 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-28 12:46 Amir Goldstein [this message]
2022-08-28 12:46 ` [PATCH 5.10 CANDIDATE 1/7] xfs: remove infinite loop when reserving free block pool Amir Goldstein
2022-08-28 12:46 ` [PATCH 5.10 CANDIDATE 2/7] xfs: always succeed at setting the reserve pool size Amir Goldstein
2022-08-28 12:46 ` [PATCH 5.10 CANDIDATE 3/7] xfs: fix overfilling of reserve pool Amir Goldstein
2022-08-28 12:46 ` [PATCH 5.10 CANDIDATE 4/7] xfs: fix soft lockup via spinning in filestream ag selection loop Amir Goldstein
2022-08-28 12:46 ` [PATCH 5.10 CANDIDATE 5/7] xfs: revert "xfs: actually bump warning counts when we send warnings" Amir Goldstein
2022-08-28 12:46 ` [PATCH 5.10 CANDIDATE 6/7] xfs: reorder iunlink remove operation in xfs_ifree Amir Goldstein
2022-08-28 12:46 ` [PATCH 5.10 CANDIDATE 7/7] xfs: validate inode fork size against fork format Amir Goldstein
2022-08-29 14:21 ` [PATCH 5.10 CANDIDATE 0/7] xfs stable candidate patches for 5.10.y (from v5.18+) Darrick J. Wong
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=20220828124614.2190592-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=leah.rumancik@gmail.com \
--cc=linux-xfs@vger.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;
as well as URLs for NNTP newsgroup(s).