linux-kernel - Re: user-mode stack size & location

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:	Tue, 28 Aug 2007 09:45:48 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Clemens Kolbitsch <clemens.kol@....at>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: user-mode stack size & location

On Tue, 28 Aug 2007 18:25:01 +0200
Clemens Kolbitsch <clemens.kol@....at> wrote:
> i see that the aout-, elf-, etc. handlers all set this variable -->
> is this the only location where it can be set?
> 
> 2.) when looking at /proc/PID/maps, i see that the stack always ends
> at different locations (obviously close to TASK_SIZE). thus the sizes
> seem to vary. where are they set / where are the infos written to the
> vma's / the PGD?
> 
> any help would be greatly appreciated!!
\

hi,

if you look where arch_align_stack() gets called.. that's where you
want to look. arch_align_stack() gets invoked in code that selects
userspace stack pointers....

Greetings,
   Arjan van de Ven
-
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/