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 00/17] xfs stable patches for 5.4.y (from v5.5)
Date: Thu, 22 Sep 2022 12:04:08 +0200 [thread overview]
Message-ID: <YywzGEFApUMalXNn@kroah.com> (raw)
In-Reply-To: <871qs3pwu9.fsf@debian-BULLSEYE-live-builder-AMD64>
On Thu, Sep 22, 2022 at 02:46:16PM +0530, Chandan Babu R wrote:
> On Wed, Sep 21, 2022 at 05:33:59 PM +0200, Greg KH wrote:
> > On Wed, Sep 21, 2022 at 11:01:33AM +0200, Greg KH wrote:
> >> On Wed, Sep 21, 2022 at 08:53:35AM +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.
> >> >
> [...]
> >> >
> >>
> >> All now queued up, thanks.
> >
> > Any specific reason why you didn't also include 2 other commits in this
> > series, that fix issues that were created by some patches in this
> > series?
> >
> > I am referring to:
> > 496b9bcd62b0 ("xfs: fix use-after-free when aborting corrupt attr inactivation")
> > 6da1b4b1ab36 ("xfs: fix an ABBA deadlock in xfs_rename")
> >
>
> I had not considered the possibility of fixes introducing regressions. I will
> test these patches and send them to the mailing list soon. Thanks for pointing
> out the missing patches.
Ok, let me drop these from the queue right now then, so that we don't
end up adding more problems then you are fixing :)
Please resend the whole new series again when they are ready.
thanks,
greg k-h
prev parent reply other threads:[~2022-09-22 10:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 3:23 [PATCH 5.4 00/17] xfs stable patches for 5.4.y (from v5.5) Chandan Babu R
2022-09-21 3:23 ` [PATCH 5.4 01/17] MAINTAINERS: add Chandan as xfs maintainer for 5.4.y Chandan Babu R
2022-09-21 3:23 ` [PATCH 5.4 02/17] iomap: iomap that extends beyond EOF should be marked dirty Chandan Babu R
2022-09-21 3:23 ` [PATCH 5.4 03/17] xfs: replace -EIO with -EFSCORRUPTED for corrupt metadata Chandan Babu R
2022-09-21 3:23 ` [PATCH 5.4 04/17] xfs: slightly tweak an assert in xfs_fs_map_blocks Chandan Babu R
2022-09-21 3:23 ` [PATCH 5.4 05/17] xfs: add missing assert in xfs_fsmap_owner_from_rmap Chandan Babu R
2022-09-21 3:23 ` [PATCH 5.4 06/17] xfs: range check ri_cnt when recovering log items Chandan Babu R
2022-09-21 3:23 ` [PATCH 5.4 07/17] xfs: attach dquots and reserve quota blocks during unwritten conversion Chandan Babu R
2022-09-21 3:23 ` [PATCH 5.4 08/17] xfs: Fix deadlock between AGI and AGF when target_ip exists in xfs_rename() Chandan Babu R
2022-09-21 3:23 ` [PATCH 5.4 09/17] xfs: convert EIO to EFSCORRUPTED when log contents are invalid Chandan Babu R
2022-09-21 3:23 ` [PATCH 5.4 10/17] xfs: constify the buffer pointer arguments to error functions Chandan Babu R
2022-09-21 3:23 ` [PATCH 5.4 11/17] xfs: always log corruption errors Chandan Babu R
2022-09-21 3:23 ` [PATCH 5.4 12/17] xfs: fix some memory leaks in log recovery Chandan Babu R
2022-09-21 3:23 ` [PATCH 5.4 13/17] xfs: stabilize insert range start boundary to avoid COW writeback race Chandan Babu R
2022-09-21 3:23 ` [PATCH 5.4 14/17] xfs: use bitops interface for buf log item AIL flag check Chandan Babu R
2022-09-21 3:23 ` [PATCH 5.4 15/17] xfs: refactor agfl length computation function Chandan Babu R
2022-09-21 3:23 ` [PATCH 5.4 16/17] xfs: split the sunit parameter update into two parts Chandan Babu R
2022-09-21 3:23 ` [PATCH 5.4 17/17] xfs: don't commit sunit/swidth updates to disk if that would cause repair failures Chandan Babu R
2022-09-21 9:01 ` [PATCH 5.4 00/17] xfs stable patches for 5.4.y (from v5.5) Greg KH
2022-09-21 15:33 ` Greg KH
2022-09-22 9:16 ` Chandan Babu R
2022-09-22 10:04 ` 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=YywzGEFApUMalXNn@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