From: Russ Anderson <rja@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
torvalds@linux-foundation.org, tony.luck@intel.com,
clameter@sgi.com
Subject: Re: [PATCH 1/2] mm: Avoid putting a bad page back on the LRU
Date: Tue, 29 Apr 2008 21:47:47 +0000 [thread overview]
Message-ID: <20080429214747.GA11617@sgi.com> (raw)
In-Reply-To: <20080429143329.3a17ef91.akpm@linux-foundation.org>
On Tue, Apr 29, 2008 at 02:33:29PM -0700, Andrew Morton wrote:
> On Mon, 28 Apr 2008 14:23:58 -0500
> Russ Anderson <rja@sgi.com> wrote:
>
> > --- test.orig/include/linux/kernel.h 2008-04-25 15:22:07.640501421 -0500
> > +++ test/include/linux/kernel.h 2008-04-25 15:42:02.826266036 -0500
> > @@ -412,6 +412,7 @@ struct sysinfo {
> > unsigned long totalhigh; /* Total high memory size */
> > unsigned long freehigh; /* Available high memory size */
> > unsigned int mem_unit; /* Memory unit size in bytes */
> > + unsigned int badpages; /* Number of bad (PG_memerror) pages */
> > char _f[20-2*sizeof(long)-sizeof(int)]; /* Padding: libc5 uses this.. */
> > };
>
> eek. sys_sysinfo() copies this structure out to userspace verbatim.
> Increasing its size by four bytes will cause memory scribbles in userspace
> applications.
>
> That's fixable by suitably adjusting sysinfo._f, but given the lack of
> version information in the sysinfo struct, I'm not sure how useful this
> change really is.
OK. The only reason badpages was added was to print the number
of page pages in /proc/meminfo. I'll go with plan B, a badmem driver
for displaying bad page info.
--
Russ Anderson, OS RAS/Partitioning Project Lead
SGI - Silicon Graphics Inc rja@sgi.com
WARNING: multiple messages have this Message-ID (diff)
From: Russ Anderson <rja@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
torvalds@linux-foundation.org, tony.luck@intel.com,
clameter@sgi.com
Subject: Re: [PATCH 1/2] mm: Avoid putting a bad page back on the LRU
Date: Tue, 29 Apr 2008 16:47:47 -0500 [thread overview]
Message-ID: <20080429214747.GA11617@sgi.com> (raw)
In-Reply-To: <20080429143329.3a17ef91.akpm@linux-foundation.org>
On Tue, Apr 29, 2008 at 02:33:29PM -0700, Andrew Morton wrote:
> On Mon, 28 Apr 2008 14:23:58 -0500
> Russ Anderson <rja@sgi.com> wrote:
>
> > --- test.orig/include/linux/kernel.h 2008-04-25 15:22:07.640501421 -0500
> > +++ test/include/linux/kernel.h 2008-04-25 15:42:02.826266036 -0500
> > @@ -412,6 +412,7 @@ struct sysinfo {
> > unsigned long totalhigh; /* Total high memory size */
> > unsigned long freehigh; /* Available high memory size */
> > unsigned int mem_unit; /* Memory unit size in bytes */
> > + unsigned int badpages; /* Number of bad (PG_memerror) pages */
> > char _f[20-2*sizeof(long)-sizeof(int)]; /* Padding: libc5 uses this.. */
> > };
>
> eek. sys_sysinfo() copies this structure out to userspace verbatim.
> Increasing its size by four bytes will cause memory scribbles in userspace
> applications.
>
> That's fixable by suitably adjusting sysinfo._f, but given the lack of
> version information in the sysinfo struct, I'm not sure how useful this
> change really is.
OK. The only reason badpages was added was to print the number
of page pages in /proc/meminfo. I'll go with plan B, a badmem driver
for displaying bad page info.
--
Russ Anderson, OS RAS/Partitioning Project Lead
SGI - Silicon Graphics Inc rja@sgi.com
next prev parent reply other threads:[~2008-04-29 21:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 19:23 [PATCH 1/2] mm: Avoid putting a bad page back on the LRU Russ Anderson
2008-04-28 19:23 ` Russ Anderson
2008-04-28 19:39 ` Christoph Lameter
2008-04-28 19:39 ` Christoph Lameter
2008-04-29 21:33 ` Andrew Morton
2008-04-29 21:33 ` Andrew Morton
2008-04-29 14:17 ` Arjan van de Ven
2008-04-29 14:17 ` Arjan van de Ven
2008-04-29 21:47 ` Russ Anderson [this message]
2008-04-29 21:47 ` Russ Anderson
2008-07-18 20:36 ` [PATCH 1/2] mm: Avoid putting a bad page back on the LRU v7 Russ Anderson
2008-07-18 20:36 ` Russ Anderson
2008-07-22 2:42 ` Nick Piggin
2008-07-22 2:42 ` Nick Piggin
2008-07-23 22:13 ` Russ Anderson
2008-07-23 22:13 ` Russ Anderson
2008-07-24 0:44 ` Nick Piggin
2008-07-24 0:44 ` Nick Piggin
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=20080429214747.GA11617@sgi.com \
--to=rja@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.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.