[lkml]   [2020]   [Jun]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 4.19 011/131] btrfs: make caching_thread use btrfs_find_next_key
On Mon 2020-06-29 11:33:02, Sasha Levin wrote:
> From: Josef Bacik <>
> [ Upstream commit 6a9fb468f1152d6254f49fee6ac28c3cfa3367e5 ]
> extent-tree.c has a find_next_key that just walks up the path to find
> the next key, but it is used for both the caching stuff and the snapshot
> delete stuff. The snapshot deletion stuff is special so it can't really
> use btrfs_find_next_key, but the caching thread stuff can. We just need
> to fix btrfs_find_next_key to deal with ->skip_locking and then it works
> exactly the same as the private find_next_key helper.
> Signed-off-by: Josef Bacik <>
> Signed-off-by: David Sterba <>
> Signed-off-by: Sasha Levin <>

According to changelog, this is not known to fix a bug. Why is it
needed in stable?

Best regards,

(cesky, pictures)
[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2020-06-30 23:10    [W:0.386 / U:43.104 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site