linux-kernel - Re: [PATCH 2/2] rename thread

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]

Date:	Thu, 3 May 2007 12:52:32 +0200 (CEST)
From:	Roman Zippel <zippel@...ux-m68k.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] rename thread_info to stack

Hi,

On Wed, 2 May 2007, Andrew Morton wrote:

> On Tue, 1 May 2007 02:10:34 +0200 (CEST) Roman Zippel <zippel@...ux-m68k.org> wrote:
> 
> > This finally renames the thread_info field in task structure to stack,
> > so that the assumptions about this field are gone and archs have more
> > freedom about placing the thread_info structure.
> 
> It's been a year or so and I've forgotten what the actual point to these
> changes is.  Can we be reminded please?

Nonbroken archs which have a proper thread pointer can do the access to 
both current thread and task structure via a single pointer.
It'll allow for a few more cleanups of the fork code, from which e.g. ia64 
could benefit.

bye, Roman
-
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/