linux-kernel - should all THREAD_SIZE macros be defined in 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>] [day] [month] [year] [list]

Date:	Wed, 12 Dec 2007 13:45:52 -0500 (EST)
From:	"Robert P. J. Day" <rpjday@...shcourse.ca>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: should all THREAD_SIZE macros be defined in thread_info.h headers?

  just asking, given that:

include/asm-x86/page_64.h:#define THREAD_SIZE  (PAGE_SIZE << THREAD_ORDER)
include/asm-arm/page-nommu.h:#define KTHREAD_SIZE (8192)
include/asm-arm/page-nommu.h:#define KTHREAD_SIZE PAGE_SIZE
include/asm-cris/processor.h:#define THREAD_SIZE       PAGE_SIZE
include/asm-m32r/processor.h:#define THREAD_SIZE (2*PAGE_SIZE)
include/asm-m68k/page.h:#define THREAD_SIZE (8192)

  all other arches seem to define that in their respective
thread_info.h headers.

rday

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
========================================================================
--
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/