[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230824143112.GA31208@redhat.com>
Date: Thu, 24 Aug 2023 16:31:12 +0200
From: Oleg Nesterov <oleg@...hat.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
peterz@...hat.com, linux-kernel@...r.kernel.org
Subject: [PATCH 0/2] introduce __next_thread(), change next_thread()
Hello,
After document-while_each_thread-change-first_tid-to-use-for_each_thread.patch
in mm tree + this series
1. We have only one lockless user of next_thread(), task_group_seq_get_next().
I think it should be changed too.
2. We have only one user of task_struct->thread_group, thread_group_empty().
The next patches will change thread_group_empty() and kill ->thread_group.
Oleg.
Powered by blists - more mailing lists