linux-kernel - 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-next>] [day] [month] [year] [list]

Date:	Tue, 28 Aug 2007 18:25:01 +0200
From:	Clemens Kolbitsch <clemens.kol@....at>
To:	linux-kernel@...r.kernel.org
Subject: user-mode stack size & location

hi!
i'm working on a new concept of i386 memory management and have to change 
quite a bit of the linux mm. could someone please point out, where the 
location & size of the USER-MODE stack is set for a new program (i.e. after 
calling sys_execve...) exactly?

I know that all settings are simply copied from the parent-process when 
invoking fork and how the stack grows (through page-faults).

However,

1.) is

  mm->start_stack

set inside the

  search_binary_handler / the individual fs-handlers?

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!!
greets,
  clemens
-
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/