From: Oleg Nesterov <oleg@redhat.com>
To: Pavel Begunkov <asml.silence@gmail.com>
Cc: io-uring@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Andrew Morton <akpm@linux-foundation.org>,
Christian Brauner <brauner@kernel.org>,
Tycho Andersen <tandersen@netflix.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Julian Orth <ju.orth@gmail.com>,
Peter Zijlstra <peterz@infradead.org>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH v3 2/2] kernel: rerun task_work while freezing in get_signal()
Date: Wed, 10 Jul 2024 21:18:24 +0200 [thread overview]
Message-ID: <20240710191824.GD9228@redhat.com> (raw)
In-Reply-To: <89ed3a52933370deaaf61a0a620a6ac91f1e754d.1720634146.git.asml.silence@gmail.com>
I have already acked this patch, so I am sorry for the noise, but
On 07/10, Pavel Begunkov wrote:
>
> Run task_works in the freezer path. Keep the patch small and simple
> so it can be easily back ported,
Agreed.
I tried to argue with v1 which added the additional task_work_run()
into get_signal(), but I failed to suggest a "better" change which
doesn't uglify/complicate get_signal/backporting.
Oleg.
next prev parent reply other threads:[~2024-07-10 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 17:58 [PATCH v3 0/2] fix task_work interation with freezing Pavel Begunkov
2024-07-10 17:58 ` [PATCH v3 1/2] io_uring/io-wq: limit retrying worker initialisation Pavel Begunkov
2024-07-10 17:58 ` [PATCH v3 2/2] kernel: rerun task_work while freezing in get_signal() Pavel Begunkov
2024-07-10 19:18 ` Oleg Nesterov [this message]
2024-07-11 7:54 ` [PATCH v3 0/2] fix task_work interation with freezing Jens Axboe
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=20240710191824.GD9228@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=io-uring@vger.kernel.org \
--cc=ju.orth@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tandersen@netflix.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
/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.