From: Andrea Arcangeli <andrea@suse.de>
To: Ben LaHaise <bcrl@redhat.com>
Cc: linux-mm@kvack.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Arjan van de Ven <arjanv@redhat.com>
Subject: Re: [PATCH] /proc/meminfo (fwd)
Date: Wed, 5 Sep 2001 21:45:52 +0200 [thread overview]
Message-ID: <20010905214552.B32584@athlon.random> (raw)
In-Reply-To: <Pine.LNX.4.33.0109051538400.16684-100000@toomuch.toronto.redhat.com>; from bcrl@redhat.com on Wed, Sep 05, 2001 at 03:38:57PM -0400
On Wed, Sep 05, 2001 at 03:38:57PM -0400, Ben LaHaise wrote:
> Heyo,
>
> Below is a patch to fix overflows in /proc/meminfo on machines with lots
> of highmem. I wish I had 64GB. Dell was right -- I was reading the
> MemTotal: line automatically instead of Mem:.
I fixed such bug ages ago:
ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.10pre4aa1/00_meminfo-wraparound-2
Andrea
--
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/
next prev parent reply other threads:[~2001-09-05 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 19:38 Ben LaHaise
2001-09-05 19:45 ` Andrea Arcangeli [this message]
2001-09-05 20:00 ` Ben LaHaise
2001-09-05 20:08 ` Andrea Arcangeli
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=20010905214552.B32584@athlon.random \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=bcrl@redhat.com \
--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