From: Baokun Li <libaokun@huaweicloud.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>, netfs@lists.linux.dev
Cc: dhowells@redhat.com, jlayton@kernel.org, zhujia.zj@bytedance.com,
jefflexu@linux.alibaba.com, linux-cachefs@redhat.com,
linux-erofs@lists.ozlabs.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
Joseph Qi <joseph.qi@linux.alibaba.com>,
Baokun Li <libaokun1@huawei.com>,
libaokun@huaweicloud.com
Subject: Re: [PATCH 5/5] cachefiles: add missing lock protection when polling
Date: Wed, 24 Apr 2024 14:23:46 +0800 [thread overview]
Message-ID: <82ba7a6b-97d1-a0f2-8360-91fbdba610a3@huaweicloud.com> (raw)
In-Reply-To: <de9d403c-c4ed-46c5-a572-18dc48bbd204@linux.alibaba.com>
Hi Xiang,
On 2024/4/24 12:29, Gao Xiang wrote:
> Hi Baokun,
>
> On 2024/4/24 11:34, libaokun@huaweicloud.com wrote:
>> From: Jingbo Xu <jefflexu@linux.alibaba.com>
>>
>> Add missing lock protection in poll routine when iterating xarray,
>> otherwise:
>>
>> Even with RCU read lock held, only the slot of the radix tree is
>> ensured to be pinned there, while the data structure (e.g. struct
>> cachefiles_req) stored in the slot has no such guarantee. The poll
>> routine will iterate the radix tree and dereference cachefiles_req
>> accordingly. Thus RCU read lock is not adequate in this case and
>> spinlock is needed here.
>>
>> Fixes: b817e22b2e91 ("cachefiles: narrow the scope of triggering
>> EPOLLIN events in ondemand mode")
>> Signed-off-by: Jingbo Xu <jefflexu@linux.alibaba.com>
>> Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>
>> Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com>
>
> I'm not sure why this patch didn't send upstream,
> https://gitee.com/anolis/cloud-kernel/commit/324ecaaa10fefb0e3d94b547e3170e40b90cda1f
>
>
Yes, this issue blocks our tests, so this commit is adapted to upstream
here.
> But since we're now working on upstreaming, so let's drop
> the previous in-house review tags..
>
> Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com>
>
> Thanks,
> Gao Xiang
Ok, thanks for the review!
Cheers,
Baokun
>
>> Signed-off-by: Baokun Li <libaokun1@huawei.com>
>> ---
>> fs/cachefiles/daemon.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/cachefiles/daemon.c b/fs/cachefiles/daemon.c
>> index 6465e2574230..73ed2323282a 100644
>> --- a/fs/cachefiles/daemon.c
>> +++ b/fs/cachefiles/daemon.c
>> @@ -365,14 +365,14 @@ static __poll_t cachefiles_daemon_poll(struct
>> file *file,
>> if (cachefiles_in_ondemand_mode(cache)) {
>> if (!xa_empty(&cache->reqs)) {
>> - rcu_read_lock();
>> + xas_lock(&xas);
>> xas_for_each_marked(&xas, req, ULONG_MAX,
>> CACHEFILES_REQ_NEW) {
>> if (!cachefiles_ondemand_is_reopening_read(req)) {
>> mask |= EPOLLIN;
>> break;
>> }
>> }
>> - rcu_read_unlock();
>> + xas_unlock(&xas);
>> }
>> } else {
>> if (test_bit(CACHEFILES_STATE_CHANGED, &cache->flags))
next prev parent reply other threads:[~2024-04-24 6:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 3:34 [PATCH 0/5] cachefiles: some bugfixes for clean object/send req/poll libaokun
2024-04-24 3:34 ` [PATCH 1/5] cachefiles: stop sending new request when dropping object libaokun
2024-04-24 3:34 ` [PATCH 2/5] cachefiles: flush all requests for the object that is being dropped libaokun
2024-04-24 3:34 ` [PATCH 3/5] cachefiles: flush ondemand_object_worker during clean object libaokun
2024-04-25 5:41 ` Jia Zhu
2024-04-25 6:53 ` Baokun Li
2024-04-24 3:34 ` [PATCH 4/5] cachefiles: cyclic allocation of msg_id to avoid reuse libaokun
2024-04-24 3:34 ` [PATCH 5/5] cachefiles: add missing lock protection when polling libaokun
2024-04-24 4:29 ` Gao Xiang
2024-04-24 6:23 ` Baokun Li [this message]
2024-04-24 5:46 ` Jia Zhu
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=82ba7a6b-97d1-a0f2-8360-91fbdba610a3@huaweicloud.com \
--to=libaokun@huaweicloud.com \
--cc=dhowells@redhat.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=jefflexu@linux.alibaba.com \
--cc=jlayton@kernel.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=libaokun1@huawei.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfs@lists.linux.dev \
--cc=zhujia.zj@bytedance.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;
as well as URLs for NNTP newsgroup(s).