From: Greg KH <greg@kroah.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-btrfs@vger.kernel.org, fdmanana@suse.com
Subject: Re: [PATCH stable-5.4.y 0/3] btrfs: backport hang fixes due to commit c53e9653605d
Date: Fri, 13 Aug 2021 14:26:03 +0200 [thread overview]
Message-ID: <YRZk20TQpSiGiis7@kroah.com> (raw)
In-Reply-To: <cover.1628854236.git.anand.jain@oracle.com>
On Fri, Aug 13, 2021 at 08:12:22PM +0800, Anand Jain wrote:
> Further to the commit c53e9653605d (btrfs: qgroup: try to flush qgroup
> space when we get -EDQUOT) there are three fixes as below.
>
> 6f23277a49e6 btrfs: qgroup: don't commit transaction when we already hold the handle
> 4d14c5cde5c2 btrfs: don't flush from btrfs_delayed_inode_reserve_metadata
> f9baa501b4fd btrfs: fix deadlock when cloning inline extents and using qgroups
>
> Commits 6f23277a49e6 and 4d14c5cde5c2 above are straightforward and are
> part of this series.
>
> However, commit f9baa501b4fd above is more complicated to backport.
> Furthermore, the bug mentioned in the commit f9baa501b4fd might not
> trigger on 5.4.y as its related commit 05a5a7621ce66c ("Btrfs: implement
> full reflink support for inline extents") is not backported to 5.4.y.
Queued up, thanks.
greg k-h
prev parent reply other threads:[~2021-08-13 12:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 12:12 [PATCH stable-5.4.y 0/3] btrfs: backport hang fixes due to commit c53e9653605d Anand Jain
2021-08-13 12:12 ` [PATCH 1/3] btrfs: qgroup: don't commit transaction when we already hold the handle Anand Jain
2021-08-13 12:12 ` [PATCH 2/3] btrfs: export and rename qgroup_reserve_meta Anand Jain
2021-08-13 12:21 ` Greg KH
2021-08-13 12:12 ` [PATCH 3/3] btrfs: don't flush from btrfs_delayed_inode_reserve_metadata Anand Jain
2021-08-13 12:26 ` 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=YRZk20TQpSiGiis7@kroah.com \
--to=greg@kroah.com \
--cc=anand.jain@oracle.com \
--cc=fdmanana@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.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