From: "Darrick J. Wong" <djwong@kernel.org>
To: Chandan Babu R <chandan.babu@oracle.com>
Cc: linux-xfs@vger.kernel.org, amir73il@gmail.com, leah.rumancik@gmail.com
Subject: Re: [PATCH 5.4 CANDIDATE 0/3] Fixes for patches backported to 5.4.y from v5.7
Date: Sun, 30 Oct 2022 16:43:35 -0700 [thread overview]
Message-ID: <Y18MJ95sTfdCncu+@magnolia> (raw)
In-Reply-To: <20221029135732.574729-1-chandan.babu@oracle.com>
On Sat, Oct 29, 2022 at 07:27:29PM +0530, Chandan Babu R wrote:
> Hi Darrick,
>
> Patches backported from v5.7 to 5.4.y had fixes from newer versions of
> Linux kernel. I had missed including these patches in my previous
> patchset posting.
>
> This patchset has been tested by executing fstests (via kdevops) using
> the following XFS configurations,
>
> 1. No CRC (with 512 and 4k block size).
> 2. Reflink/Rmapbt (1k and 4k block size).
> 3. Reflink without Rmapbt.
> 4. External log device.
Looks good to me!
Acked-by: Darrick J. Wong <djwong@kernel.org>
--D
>
> Brian Foster (1):
> xfs: finish dfops on every insert range shift iteration
>
> Darrick J. Wong (2):
> xfs: clear XFS_DQ_FREEING if we can't lock the dquot buffer to flush
> xfs: force the log after remapping a synchronous-writes file
>
> fs/xfs/xfs_bmap_util.c | 2 +-
> fs/xfs/xfs_file.c | 17 ++++++++++++++++-
> fs/xfs/xfs_qm.c | 1 +
> 3 files changed, 18 insertions(+), 2 deletions(-)
>
> --
> 2.35.1
>
prev parent reply other threads:[~2022-10-30 23:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 13:57 [PATCH 5.4 CANDIDATE 0/3] Fixes for patches backported to 5.4.y from v5.7 Chandan Babu R
2022-10-29 13:57 ` [PATCH 5.4 CANDIDATE 1/3] xfs: finish dfops on every insert range shift iteration Chandan Babu R
2022-10-29 13:57 ` [PATCH 5.4 CANDIDATE 2/3] xfs: clear XFS_DQ_FREEING if we can't lock the dquot buffer to flush Chandan Babu R
2022-10-29 13:57 ` [PATCH 5.4 CANDIDATE 3/3] xfs: force the log after remapping a synchronous-writes file Chandan Babu R
2022-10-30 23:43 ` Darrick J. Wong [this message]
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=Y18MJ95sTfdCncu+@magnolia \
--to=djwong@kernel.org \
--cc=amir73il@gmail.com \
--cc=chandan.babu@oracle.com \
--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