From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
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 13:06:35 -0700 [thread overview]
Message-ID: <1240862795.29485.64.camel@nimitz> (raw)
In-Reply-To: <20090427125208.94730dd8.akpm@linux-foundation.org>
On Mon, 2009-04-27 at 12:52 -0700, Andrew Morton wrote:
> 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?
Here's the version that I got. My guess would be that your copy is
sitting in some IBM mail server's queue right now. It might show up in
a couple of days. :)
---
Andrew,
Please merge the following patch.
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.
Reported-by: Dave Hansen <dave@linux.vnet.ibm.com>
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Signed-off-by: Eric B Munson <ebmunson@us.ibm.com>
---
fs/proc/meminfo.c | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/fs/proc/meminfo.c b/fs/proc/meminfo.c
index 74ea974..facb9fb 100644
--- a/fs/proc/meminfo.c
+++ b/fs/proc/meminfo.c
@@ -22,7 +22,7 @@ void __attribute__((weak)) arch_report_meminfo(struct seq_file *m)
static int meminfo_proc_show(struct seq_file *m, void *v)
{
struct sysinfo i;
- unsigned long committed;
+ long committed;
unsigned long allowed;
struct vmalloc_info vmi;
long cached;
@@ -36,6 +36,8 @@ static int meminfo_proc_show(struct seq_file *m, void *v)
si_meminfo(&i);
si_swapinfo(&i);
committed = atomic_long_read(&vm_committed_space);
+ if (committed < 0)
+ committed = 0;
allowed = ((totalram_pages - hugetlb_total_pages())
* sysctl_overcommit_ratio / 100) + total_swap_pages;
--
1.6.1.2
-- Dave
--
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>
prev parent reply other threads:[~2009-04-27 20:06 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
2009-04-27 20:06 ` Dave Hansen [this message]
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=1240862795.29485.64.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--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).