From: Chao Yu <chao@kernel.org>
To: Sandeep Dhavale <dhavale@google.com>
Cc: chao@kernel.org, linux-erofs@lists.ozlabs.org,
Gao Xiang <xiang@kernel.org>, Yue Hu <zbestahu@gmail.com>,
Jeffle Xu <jefflexu@linux.alibaba.com>,
hsiangkao@linux.alibaba.com, kernel-team@android.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] erofs: lazily initialize per-CPU workers and CPU hotplug hooks
Date: Tue, 29 Apr 2025 14:05:53 +0800 [thread overview]
Message-ID: <aced334a-e542-42b9-ade4-00f6773c2d45@kernel.org> (raw)
In-Reply-To: <CAB=BE-Ru31S1Qq0Gmi9UXtaL6k4dcLdTUa-CJbmhuXb7a2dSeQ@mail.gmail.com>
Hi Sandeep,
On 4/29/25 05:49, Sandeep Dhavale wrote:
> Hi Chao,
>
>>
>> - mount #1 - mount #2
>> - z_erofs_init_pcpu_workers
>> - atomic_xchg(, 1)
>> - z_erofs_init_pcpu_workers
>> - atomic_xchg(, 1)
>> : return 0 since atomic variable is 1
>> it will run w/o percpu workers and hotplug
>> : update atomic variable to 1
>> - erofs_init_percpu_workers
>> : fail
>> - atomic_set(, 0)
>> : update atomic variable to 0 & fail the mount
>>
>> Can we add some logs to show we succeed/fail to initialize workers or
>> hotplugs? As for mount #2, it expects it will run w/ them, but finally
>> it may not. So we'd better have a simple way to know?
>>
>> Thanks,
>>
> What you have laid out as race, indeed can happen if
> erofs_init_percpu_workers() fails with ENOMEM. For me that is still
> not catastrophic as workqueue fallback is in place so the filesystem
> is still functional. And at the next mount, the logic will be
> reattempted as the atomic variable is reset to 0 after failure.
Yeah, correct.
>
> If you still think we need to have a log message, I will be happy to
> spin up the next revision with logging for ENOMEM.
I guess it will be good to add log for such case, thanks. :)
Thanks,
>
> Thanks for the review!
>
> Regards,
> Sandeep.
prev parent reply other threads:[~2025-04-29 6:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 6:10 [PATCH v4] erofs: lazily initialize per-CPU workers and CPU hotplug hooks Sandeep Dhavale
2025-04-24 0:31 ` Gao Xiang
2025-04-24 6:04 ` Sandeep Dhavale
2025-04-24 12:02 ` Gao Xiang
2025-04-24 3:03 ` Hongbo Li
2025-04-25 2:15 ` Chao Yu
2025-04-28 21:49 ` Sandeep Dhavale
2025-04-29 6:05 ` Chao Yu [this message]
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=aced334a-e542-42b9-ade4-00f6773c2d45@kernel.org \
--to=chao@kernel.org \
--cc=dhavale@google.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=jefflexu@linux.alibaba.com \
--cc=kernel-team@android.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiang@kernel.org \
--cc=zbestahu@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.