[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250210124340.GD32480@redhat.com>
Date: Mon, 10 Feb 2025 13:43:41 +0100
From: Oleg Nesterov <oleg@...hat.com>
To: Frederic Weisbecker <frederic@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Valentin Schneider <vschneid@...hat.com>,
Marcelo Tosatti <mtosatti@...hat.com>,
Vlastimil Babka <vbabka@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
Michal Hocko <mhocko@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>, linux-mm@...ck.org
Subject: Re: [PATCH 1/6 v2] task_work: Provide means to check if a work is
queued
On 02/09, Frederic Weisbecker wrote:
>
> @@ -56,6 +56,8 @@ int task_work_add(struct task_struct *task, struct callback_head *work,
> {
> struct callback_head *head;
>
> + work->next = TASK_WORK_DEQUEUED;
Do we really need to do this at the start of task_work_add() ?
If the caller didn't do init_task_work() before and task_work_add()
returns -EINVAL we probably do not care?
Reviewed-by: Oleg Nesterov <oleg@...hat.com>
Powered by blists - more mailing lists