[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <57afbcf7-df1f-47b8-2b81-8fca87487f57@huaweicloud.com>
Date: Wed, 11 Jan 2023 12:03:48 +0800
From: Hou Tao <houtao@...weicloud.com>
To: linux-cachefs@...hat.com
Cc: David Howells <dhowells@...hat.com>,
Jeff Layton <jlayton@...nel.org>, linux-erofs@...ts.ozlabs.org,
linux-kernel@...r.kernel.org,
Jingbo Xu <jefflexu@...ux.alibaba.com>,
"houtao1@...wei.com" <houtao1@...wei.com>
Subject: Re: [PATCH v2 0/2] Fixes for fscache volume operations
ping ?
On 12/26/2022 6:33 PM, Hou Tao wrote:
> From: Hou Tao <houtao1@...wei.com>
>
> Hi,
>
> The patchset includes two fixes for fscache volume operations: patch 1
> fixes the hang problem during volume acquisition when the volume
> acquisition process waits for the freeing of relinquished volume, patch
> 2 adds the missing memory barrier in fscache_create_volume_work() and it
> is spotted through code review when checking whether or not these is
> missing smp_mb() before invoking wake_up_bit().
>
> Comments are always welcome.
>
> Chang Log:
> v2:
> * rebased on v6.1-rc1
> * Patch 1: use wait_on_bit() instead (Suggested by David)
> * Patch 2: add the missing smp_mb() in fscache_create_volume_work()
>
> v1: https://listman.redhat.com/archives/linux-cachefs/2022-December/007384.html
>
> Hou Tao (2):
> fscache: Use wait_on_bit() to wait for the freeing of relinquished
> volume
> fscache: Add the missing smp_mb__after_atomic() before wake_up_bit()
>
> fs/fscache/volume.c | 17 ++++++++++++++---
> 1 file changed, 14 insertions(+), 3 deletions(-)
>
Powered by blists - more mailing lists