linux-kernel - [2.6.23(?)=<] X used greatest stack depth: N bytes left

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]

Date:	Fri, 28 Dec 2007 22:11:25 +0100
From:	"Oliver Pinter (Pintér Olivér)" 
	<oliver.pntr@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: [2.6.23(?)=<] X used greatest stack depth: N bytes left

in newer kernel I recently see this warnings:

X used greatest stack depth: N bytes left

X E { program name }
N E { x byte }

----------------8<--------------
...
khelper used greatest stack depth: 7496 bytes left
khelper used greatest stack depth: 7184 bytes left
...
khelper used greatest stack depth: 6328 bytes left
stty used greatest stack depth: 6180 bytes left
mount used greatest stack depth: 6156 bytes left
mknod used greatest stack depth: 5932 bytes left
...
wpa_supplicant used greatest stack depth: 5740 bytes left
...
dhclient3 used greatest stack depth: 5500 bytes left
----------------8<--------------

it is the "results" of the CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_STACK_USAGE=y options or it's other problem or feature?

-- 
Thanks,
Oliver
--
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/