[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <172068446669.395668.14041206933640697434.b4-ty@kernel.dk>
Date: Thu, 11 Jul 2024 01:54:26 -0600
From: Jens Axboe <axboe@...nel.dk>
To: io-uring@...r.kernel.org, Pavel Begunkov <asml.silence@...il.com>
Cc: Oleg Nesterov <oleg@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Christian Brauner <brauner@...nel.org>,
Tycho Andersen <tandersen@...flix.com>,
Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org,
Julian Orth <ju.orth@...il.com>, Peter Zijlstra <peterz@...radead.org>,
Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH v3 0/2] fix task_work interation with freezing
On Wed, 10 Jul 2024 18:58:16 +0100, Pavel Begunkov wrote:
> It's reported [1] that a task_work queued at a wrong time can prevent
> freezing and make the tasks to spin in get_signal() taking 100%
> of CPU. Patch 1 is a preparation. Patch 2 addresses the issue.
>
> [1] https://github.com/systemd/systemd/issues/33626
>
> v3: Slightly adjust commit messages
> v2: Move task_work_run() into do_freezer_trap()
> Correct the Fixes tag is 2/2
>
> [...]
Applied, thanks!
[1/2] io_uring/io-wq: limit retrying worker initialisation
commit: 0453aad676ff99787124b9b3af4a5f59fbe808e2
[2/2] kernel: rerun task_work while freezing in get_signal()
commit: 943ad0b62e3c21f324c4884caa6cb4a871bca05c
Best regards,
--
Jens Axboe
Powered by blists - more mailing lists