linux-kernel - [PATCH 0/3] more next_thread/while_each

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-next>] [day] [month] [year] [list]

Message-ID: <20131122191803.GA16919@redhat.com>
Date:	Fri, 22 Nov 2013 20:18:03 +0100
From:	Oleg Nesterov <oleg@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Michal Hocko <mhocko@...e.cz>, Sameer Nanda <snanda@...omium.org>,
	Sergey Dyasly <dserrg@...il.com>, linux-kernel@...r.kernel.org
Subject: [PATCH 0/3] more next_thread/while_each_thread changes

Trivial, change the remaining next_thread (ab)users to use
while_each_thread().

The last user which should be changed is next_tid(), but we can't
do this now.

__exit_signal() and complete_signal() are fine, they actually need
next_thread() logic.

Oleg.

 fs/proc/array.c |    3 +--
 kernel/signal.c |    7 +++----
 kernel/sys.c    |    3 +--
 3 files changed, 5 insertions(+), 8 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/