linux-kernel - 4K Pageable Stacks a MUST

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: <AANLkTik_lsycuZNpCiPA7L594bhwSjR2XQg9VZ3CIKEB@mail.gmail.com>
Date:	Mon, 14 Jun 2010 00:34:12 -0600
From:	Jeffrey Merkey <jeffmerkey@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: 4K Pageable Stacks a MUST

I have been running down bugs on the MDB Debugger on a 4 processor AMD
Opteron System and have discovered that processors 1-X (other than 0)
use a buttload of stack space when all the spinlock debgguging checks
are turned on -- way too much memory and the systenter_past_esp panic
shows up a lot.  NetWare at one point instrumented the ability to page
map an extra 4K of memory up to 16K (then release it when the stack
shrunk back to a smaller usage footprint).  I think for debugging and
just general usage you should enable a 16K pagable limit with 4K
stacks for debuggers and such or just to stop a lot of dump traps.

It's getting to the point where 8K wont be enough when people need to
debug spinlocks and rcu locks and other types of breakage.  Would not
be hard to instrument.

Jeff
--
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/