From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: ebmunson@us.ibm.com, kosaki.motohiro@jp.fujitsu.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org, mel@csn.ul.ie,
cl@linux-foundation.org
Subject: Re: [PATCH] Display 0 in meminfo for Committed_AS when value underflows
Date: Mon, 27 Apr 2009 12:52:08 -0700 [thread overview]
Message-ID: <20090427125208.94730dd8.akpm@linux-foundation.org> (raw)
In-Reply-To: <1240848914.29485.52.camel@nimitz>
On Mon, 27 Apr 2009 09:15:14 -0700
Dave Hansen <dave@linux.vnet.ibm.com> wrote:
> On Mon, 2009-04-27 at 17:10 +0100, Eric B Munson wrote:
> > Splitting this patch from the chunk that addresses the cause of the underflow
> > because the solution still requires some discussion.
> >
> > Dave Hansen reported that under certain cirumstances the Committed_AS value
> > can underflow which causes extremely large numbers to be displayed in
> > meminfo. This patch adds an underflow check to meminfo_proc_show() for the
> > Committed_AS value. Most fields in /proc/meminfo already have an underflow
> > check, this brings Committed_AS into line.
>
> Yeah, this is the right fix for now until we can iron out the base
> issues. Eric, I think this may also be a candidate for -stable.
>
> Signed-off-by: Dave Hansen <dave@linux.vnet.ibm.com>
I cannot find Eric's original patch anywhere. Did some demented MTA munch it?
--
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:[~2009-04-27 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 16:10 [PATCH] Display 0 in meminfo for Committed_AS when value underflows Eric B Munson
2009-04-27 16:15 ` Dave Hansen
2009-04-27 16:15 ` Christoph Lameter
2009-04-27 19:52 ` Andrew Morton [this message]
2009-04-27 20:06 ` Dave Hansen
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=20090427125208.94730dd8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=ebmunson@us.ibm.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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).