linux-kernel - Re: [PATCH 0/2] introduce __next_thread(), change next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20230824144029.GA31630@redhat.com>
Date:   Thu, 24 Aug 2023 16:40:29 +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>,
        Peter Zijlstra <peterz@...radead.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] introduce __next_thread(), change next_thread()

Damn.

Peter Zijlstra's email was wrong. Fix it.

Peter, sorry, you can find this short series on kernel.org,
https://lore.kernel.org/all/20230824143112.GA31208@redhat.com/

or I can resend with your email fixed.

On 08/24, Oleg Nesterov wrote:
>
> 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.