From: Christoph Hellwig <hch@infradead.org>
To: Yiwei Zhang <zzyiwei@android.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Felix Kuehling <Felix.Kuehling@amd.com>,
Jens Axboe <axboe@kernel.dk>, Petr Mladek <pmladek@suse.com>,
"J. Bruce Fields" <bfields@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <frederic@kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
Ilias Stamatis <stamatis.iliass@gmail.com>,
Rob Clark <robdclark@chromium.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Liang Chen <cl@rock-chips.com>,
linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: Re: [PATCH] kthread: add kthread_mod_pending_delayed_work api
Date: Tue, 16 Feb 2021 09:11:28 +0000 [thread overview]
Message-ID: <20210216091128.GA3973504@infradead.org> (raw)
In-Reply-To: <20210214000611.2169820-1-zzyiwei@android.com>
On Sun, Feb 14, 2021 at 12:06:11AM +0000, Yiwei Zhang wrote:
> The existing kthread_mod_delayed_work api will queue a new work if
> failing to cancel the current work due to no longer being pending.
> However, there's a case that the same work can be enqueued from both
> an async request and a delayed work, and a racing could happen if the
> async request comes right after the timeout delayed work gets scheduled,
> because the clean up work may not be safe to run twice.
Who is going to use this? Please submit it together with the actual
user.
next prev parent reply other threads:[~2021-02-16 9:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 0:06 Yiwei Zhang
2021-02-15 13:28 ` Petr Mladek
2021-02-16 9:11 ` Christoph Hellwig [this message]
2021-02-16 18:58 ` Yiwei Zhang
2021-02-17 11:14 ` Petr Mladek
2021-02-19 6:29 ` Yiwei Zhang
2021-02-19 10:27 ` Petr Mladek
2021-02-19 10:30 ` Christoph Hellwig
2021-02-19 10:56 ` Petr Mladek
2021-02-23 0:39 ` Yiwei Zhang
2021-02-23 0:58 ` Yiwei Zhang
2021-02-23 15:52 ` Petr Mladek
2021-02-23 22:29 ` Yiwei Zhang
2021-02-24 9:34 ` Petr Mladek
2021-02-25 22:17 ` Yiwei Zhang
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=20210216091128.GA3973504@infradead.org \
--to=hch@infradead.org \
--cc=Felix.Kuehling@amd.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bfields@redhat.com \
--cc=cl@rock-chips.com \
--cc=frederic@kernel.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mtosatti@redhat.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=robdclark@chromium.org \
--cc=stamatis.iliass@gmail.com \
--cc=zzyiwei@android.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®