From: Andrew Morton <akpm@linux-foundation.org>
To: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: do not show VmExe bigger than total executable virtual memory
Date: Tue, 10 Oct 2017 15:25:04 -0700 [thread overview]
Message-ID: <20171010152504.c0b84899a95e0bcd79b73290@linux-foundation.org> (raw)
In-Reply-To: <150728955451.743749.11276392315459539583.stgit@buzz>
On Fri, 06 Oct 2017 14:32:34 +0300 Konstantin Khlebnikov <khlebnikov@yandex-team.ru> wrote:
> If start_code / end_code pointers are screwed then "VmExe" could be bigger
> than total executable virtual memory and "VmLib" becomes negative:
>
> VmExe: 294320 kB
> VmLib: 18446744073709327564 kB
>
> VmExe and VmLib documented as text segment and shared library code size.
>
> Now their sum will be always equal to mm->exec_vm which sums size of
> executable and not writable and not stack areas.
When does this happen? What causes start_code/end_code to get "screwed"?
When these pointers are screwed, the result of end_code-start_code can
still be wrong while not necessarily being negative, yes? In which
case we'll still display incorrect output?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-10-10 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 11:32 [PATCH] proc: do not show VmExe bigger than total executable virtual memory Konstantin Khlebnikov
2017-10-10 22:25 ` Andrew Morton [this message]
2017-10-11 7:00 ` Konstantin Khlebnikov
2017-12-01 17:25 ` Vlastimil Babka
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=20171010152504.c0b84899a95e0bcd79b73290@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).