All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>,
	Chandan Babu R <chandan.babu@oracle.com>,
	"Darrick J . Wong" <djwong@kernel.org>,
	Leah Rumancik <leah.rumancik@gmail.com>,
	linux-xfs@vger.kernel.org, stable@vger.kernel.org
Subject: [PATCH 5.10 0/2] Two more xfs backports for 5.10.y (from v5.11)
Date: Tue, 28 Mar 2023 10:35:10 +0300	[thread overview]
Message-ID: <20230328073512.460533-1-amir73il@gmail.com> (raw)

Greg,

Chandan is preparing a series of backports from v5.11 to 5.4.y.
These two backports were selected by Chandan for 5.4.y, but are
currently missing from 5.10.y.

Specifically, patch #2 fixes a problem seen in the wild on UEK
and the UEK kernels already carry this patch.

The patches have gone through the usual xfs test/review routine.

Thanks,
Amir.

Brian Foster (1):
  xfs: don't reuse busy extents on extent trim

Darrick J. Wong (1):
  xfs: shut down the filesystem if we screw up quota reservation

 fs/xfs/xfs_extent_busy.c | 14 --------------
 fs/xfs/xfs_trans_dquot.c | 13 ++++++++++---
 2 files changed, 10 insertions(+), 17 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-03-28  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28  7:35 Amir Goldstein [this message]
2023-03-28  7:35 ` [PATCH 5.10 1/2] xfs: shut down the filesystem if we screw up quota reservation Amir Goldstein
2023-03-28  7:35 ` [PATCH 5.10 2/2] xfs: don't reuse busy extents on extent trim Amir Goldstein
2023-03-28 13:54 ` [PATCH 5.10 0/2] Two more xfs backports for 5.10.y (from v5.11) Greg Kroah-Hartman

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=20230328073512.460533-1-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --cc=chandan.babu@oracle.com \
    --cc=djwong@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=leah.rumancik@gmail.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.