[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <348f2119-0eca-9bc9-4def-62bda459683e@suse.cz>
Date: Wed, 11 Jan 2017 17:17:30 +0100
From: Jiri Slaby <jslaby@...e.cz>
To: Jeff Mahoney <jeffm@...e.com>
Cc: Chris Mason <clm@...com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Revert "Btrfs: don't delay inode ref updates during log,
replay"
On 12/03/2016, 04:21 AM, Jeff Mahoney wrote:
> This reverts commit 644d10716875b24388680925d6c7502420987bfe.
>
> The original patch for mainline, 6f8960541b1 (Btrfs: don't delay
> inode ref updates during log replay) lists 1d52c78afbb (Btrfs: try
> not to ENOSPC on log replay) as the only pre-3.18 dependency, but it
> also depends on 67de11769bd (Btrfs: introduce the delayed inode ref
> deletion for the single link inode), which was introduced in 3.14
> and isn't in 3.12.y.
>
> The -stable commit added the check to btrfs_delayed_update_inode,
> which may look similar to btrfs_delayed_delete_inode_ref, but it's
> only superficial. The tops of both functions handle typical
Thanks, now applied after dealing with the pile of patches collected
during Christmas.
--
js
suse labs
Powered by blists - more mailing lists