From: Greg KH <gregkh@linuxfoundation.org>
To: Chandan Babu R <chandan.babu@oracle.com>
Cc: sashal@kernel.org, mcgrof@kernel.org, linux-xfs@vger.kernel.org,
stable@vger.kernel.org, djwong@kernel.org, amir73il@gmail.com,
leah.rumancik@gmail.com
Subject: Re: [PATCH 5.4 V2 00/19] xfs stable patches for 5.4.y (from v5.5)
Date: Mon, 26 Sep 2022 08:52:05 +0200 [thread overview]
Message-ID: <YzFMFWDw8iHPzYZj@kroah.com> (raw)
In-Reply-To: <20220924125656.101069-1-chandan.babu@oracle.com>
On Sat, Sep 24, 2022 at 06:26:37PM +0530, Chandan Babu R wrote:
> Hi Greg,
>
> This 5.4.y backport series contains fixes from v5.5. The patchset has
> been acked by Darrick.
>
> Changelog:
> V1 -> V2:
> 1. Added two patches which fix regressions that were introduced by
> two patches present in the V1 patchset.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-09-26 6:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 12:56 [PATCH 5.4 V2 00/19] xfs stable patches for 5.4.y (from v5.5) Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 01/19] MAINTAINERS: add Chandan as xfs maintainer for 5.4.y Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 02/19] iomap: iomap that extends beyond EOF should be marked dirty Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 03/19] xfs: replace -EIO with -EFSCORRUPTED for corrupt metadata Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 04/19] xfs: slightly tweak an assert in xfs_fs_map_blocks Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 05/19] xfs: add missing assert in xfs_fsmap_owner_from_rmap Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 06/19] xfs: range check ri_cnt when recovering log items Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 07/19] xfs: attach dquots and reserve quota blocks during unwritten conversion Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 08/19] xfs: Fix deadlock between AGI and AGF when target_ip exists in xfs_rename() Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 09/19] xfs: convert EIO to EFSCORRUPTED when log contents are invalid Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 10/19] xfs: constify the buffer pointer arguments to error functions Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 11/19] xfs: always log corruption errors Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 12/19] xfs: fix some memory leaks in log recovery Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 13/19] xfs: stabilize insert range start boundary to avoid COW writeback race Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 14/19] xfs: use bitops interface for buf log item AIL flag check Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 15/19] xfs: refactor agfl length computation function Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 16/19] xfs: split the sunit parameter update into two parts Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 17/19] xfs: don't commit sunit/swidth updates to disk if that would cause repair failures Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 18/19] xfs: fix an ABBA deadlock in xfs_rename Chandan Babu R
2022-09-24 12:56 ` [PATCH 5.4 V2 19/19] xfs: fix use-after-free when aborting corrupt attr inactivation Chandan Babu R
2022-09-26 6:52 ` Greg KH [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=YzFMFWDw8iHPzYZj@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amir73il@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=leah.rumancik@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox