From: JeffleXu <jefflexu@linux.alibaba.com>
To: Yue Hu <huyue2@coolpad.com>,
dhowells@redhat.com, linux-cachefs@redhat.com
Cc: zhangwen@coolpad.com, linux-kernel@vger.kernel.org, zbestahu@gmail.com
Subject: Re: [Linux-cachefs] [PATCH] fscache: Fix if condition in fscache_wait_on_volume_collision()
Date: Fri, 1 Jul 2022 17:03:28 +0800 [thread overview]
Message-ID: <d5cc413d-d32a-5612-fe7a-95b61892c363@linux.alibaba.com> (raw)
In-Reply-To: <20220525023212.32642-1-huyue2@coolpad.com>
On 5/25/22 10:32 AM, Yue Hu wrote:
> After waiting for the volume to complete the acquisition with timeout,
> the if condition under which potential volume collision occurs should be
> acquire the volume is still pending rather than not pending so that we
> will continue to wait until the pending flag is cleared. Also, use the
> existing test pending wrapper directly instead of test_bit().
>
> Signed-off-by: Yue Hu <huyue2@coolpad.com>
> ---
> fs/fscache/volume.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/fscache/volume.c b/fs/fscache/volume.c
> index 71d3a6d6d72c..f2009cc22002 100644
> --- a/fs/fscache/volume.c
> +++ b/fs/fscache/volume.c
> @@ -143,7 +143,7 @@ static void fscache_wait_on_volume_collision(struct fscache_volume *candidate,
> {
> wait_var_event_timeout(&candidate->flags,
> !fscache_is_acquire_pending(candidate), 20 * HZ);
> - if (!fscache_is_acquire_pending(candidate)) {
> + if (fscache_is_acquire_pending(candidate)) {
> pr_notice("Potential volume collision new=%08x old=%08x",
> candidate->debug_id, collidee_debug_id);
> fscache_stat(&fscache_n_volumes_collision);
Yeah, I also noticed that before.
> @@ -182,7 +182,7 @@ static bool fscache_hash_volume(struct fscache_volume *candidate)
> hlist_bl_add_head(&candidate->hash_link, h);
> hlist_bl_unlock(h);
>
> - if (test_bit(FSCACHE_VOLUME_ACQUIRE_PENDING, &candidate->flags))
> + if (fscache_is_acquire_pending(candidate))
> fscache_wait_on_volume_collision(candidate, collidee_debug_id);
> return true;
>
LGTM.
Reviewed-by: Jeffle Xu <jefflexu@linux.alibaba.com>
--
Thanks,
Jeffle
next prev parent reply other threads:[~2022-07-01 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220525023212.32642-1-huyue2@coolpad.com>
2022-05-26 9:37 ` Gao Xiang
2022-07-01 9:03 ` JeffleXu [this message]
2022-07-05 14:59 ` Jeff Layton
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=d5cc413d-d32a-5612-fe7a-95b61892c363@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=dhowells@redhat.com \
--cc=huyue2@coolpad.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zbestahu@gmail.com \
--cc=zhangwen@coolpad.com \
/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
all inboxes | Powered by JetHome®