Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1556679 > unrolled thread

Re: [PATCH] Revert "Btrfs: don't delay inode ref updates during log, replay"

Started byJiri Slaby <jslaby@suse.cz>
First post2017-01-11 17:20 +0100
Last post2017-01-11 17:20 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH] Revert "Btrfs: don't delay inode ref updates during log,  replay" Jiri Slaby <jslaby@suse.cz> - 2017-01-11 17:20 +0100

#1556679 — Re: [PATCH] Revert "Btrfs: don't delay inode ref updates during log, replay"

FromJiri Slaby <jslaby@suse.cz>
Date2017-01-11 17:20 +0100
SubjectRe: [PATCH] Revert "Btrfs: don't delay inode ref updates during log, replay"
Message-ID<sYtN0-Fd-39@gated-at.bofh.it>
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

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web