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] [day] [month] [year] [list]
Message-ID: <780b9e4e-7405-2266-a589-17a182d7c7da@redhat.com>
Date:   Mon, 27 Nov 2017 12:33:18 +0100
From:   Florian Weimer <fweimer@...hat.com>
To:     Xishi Qiu <qiuxishi@...wei.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Linux MM <linux-mm@...ck.org>
Cc:     zhong jiang <zhongjiang@...wei.com>
Subject: Re: [RFC] a question about stack size form /proc/pid/task/child
 pid/limits

On 09/06/2017 04:14 AM, Xishi Qiu wrote:
> Hi, I find if I use a defined stack size to create a child thread,
> then the max stack size from /proc/pid/task/child pid/limits still
> shows "Max stack size            8388608", it doesn't update to
> the user defined size, is it a problem?

This reflects the maximum stack size of the main thread after execve. 
The size of the stack of the current thread is a separate matter; it can 
be located anywhere in the process image and much smaller or larger than 
the maximum size of the initial stack of the main thread.

Thanks,
Florian

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ