From: Cyrill Gorcunov <gorcunov@gmail.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Tejun Heo <tj@kernel.org>, Andrew Vagin <avagin@openvz.org>,
Serge Hallyn <serge.hallyn@canonical.com>,
Vasiliy Kulikov <segoon@openwall.com>,
Kees Cook <keescook@chromium.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fs, proc: Add start_data, end_data, start_brk members to /proc/$pid/stat v2
Date: Wed, 7 Dec 2011 10:33:08 +0400 [thread overview]
Message-ID: <20111207063308.GC20459@moon> (raw)
In-Reply-To: <20111207090259.e2296dd3.kamezawa.hiroyu@jp.fujitsu.com>
On Wed, Dec 07, 2011 at 09:02:59AM +0900, KAMEZAWA Hiroyuki wrote:
> On Wed, 7 Dec 2011 02:53:15 +0400
> Cyrill Gorcunov <gorcunov@gmail.com> wrote:
>
> > Index: linux-2.6.git/Documentation/filesystems/proc.txt
> > ===================================================================
> > --- linux-2.6.git.orig/Documentation/filesystems/proc.txt
> > +++ linux-2.6.git/Documentation/filesystems/proc.txt
> > @@ -305,6 +305,9 @@ Table 1-4: Contents of the stat files (a
> > blkio_ticks time spent waiting for block IO
> > gtime guest time of the task in jiffies
> > cgtime guest time of the task children in jiffies
> > + start_data address above which program data is placed
> > + end_data address above which program data is placed
> > + start_brk address above which program data can be expanded with brk() call
> > ..............................................................................
> >
> nitpick.
>
> After reading Wikipedia, http://en.wikipedia.org/wiki/Data_segment
>
> I prefer
>
> start_data address above program data+bss is placed.
> end_data address below program data+bss is placed
> start_break address above which program heap can be expaned with brk() call
>
> rather than just 'data'.
>
No problem, I'll update (These segments are filled by binfmt handlers).
Cyrill
next prev parent reply other threads:[~2011-12-07 6:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 18:20 [PATCH] fs, proc: Add start_data, end_data, start_brk members to /proc/$pid/stat v2 Cyrill Gorcunov
2011-12-06 22:08 ` Andrew Morton
2011-12-06 22:15 ` Cyrill Gorcunov
2011-12-06 22:53 ` Cyrill Gorcunov
2011-12-06 23:22 ` Kees Cook
2011-12-07 6:31 ` Cyrill Gorcunov
2011-12-07 0:02 ` KAMEZAWA Hiroyuki
2011-12-07 6:33 ` Cyrill Gorcunov [this message]
2011-12-07 7:07 ` Cyrill Gorcunov
2011-12-12 7:30 ` Eric W. Biederman
2011-12-12 7:38 ` Cyrill Gorcunov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111207063308.GC20459@moon \
--to=gorcunov@gmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=avagin@openvz.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=segoon@openwall.com \
--cc=serge.hallyn@canonical.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.