From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: davem@davemloft.net, riel@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH/RFT 4/5] CLOCK-Pro page replacement
Date: Fri, 19 Aug 2005 17:27:06 +1000 [thread overview]
Message-ID: <1124436426.23757.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20050819001030.52ec1364.akpm@osdl.org>
On Fri, 2005-08-19 at 00:10 -0700, Andrew Morton wrote:
> Rusty Russell <rusty@rustcorp.com.au> wrote:
> > I believe we just ignored sparc64. That usually works for solving these
> > kind of bugs. 8)
>
> heh. iirc, it was demonstrable on x86 also.
No. gcc-2.95 on Sparc64 put uninititialized vars into the bss, ignoring
the __attribute__((section(".data.percpu"))) directive. x86 certainly
doesn't have this, I just tested it w/2.95.
Really, it's Sparc64 + gcc-2.95. Send an urgent telegram to the user
telling them to upgrade.
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: davem@davemloft.net, riel@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH/RFT 4/5] CLOCK-Pro page replacement
Date: Fri, 19 Aug 2005 17:27:06 +1000 [thread overview]
Message-ID: <1124436426.23757.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20050819001030.52ec1364.akpm@osdl.org>
On Fri, 2005-08-19 at 00:10 -0700, Andrew Morton wrote:
> Rusty Russell <rusty@rustcorp.com.au> wrote:
> > I believe we just ignored sparc64. That usually works for solving these
> > kind of bugs. 8)
>
> heh. iirc, it was demonstrable on x86 also.
No. gcc-2.95 on Sparc64 put uninititialized vars into the bss, ignoring
the __attribute__((section(".data.percpu"))) directive. x86 certainly
doesn't have this, I just tested it w/2.95.
Really, it's Sparc64 + gcc-2.95. Send an urgent telegram to the user
telling them to upgrade.
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
--
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:[~2005-08-19 7:27 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 20:02 [PATCH/RFT 0/5] CLOCK-Pro page replacement Rik van Riel
2005-08-10 20:02 ` Rik van Riel
2005-08-10 20:02 ` [PATCH/RFT 1/5] " Rik van Riel
2005-08-10 20:02 ` Rik van Riel
2005-08-10 20:02 ` [PATCH/RFT 2/5] " Rik van Riel
2005-08-10 20:02 ` Rik van Riel
2005-08-10 20:27 ` David S. Miller
2005-08-10 20:27 ` David S. Miller, Rik van Riel
2005-08-10 20:38 ` Rik van Riel
2005-08-10 20:38 ` Rik van Riel
2005-08-10 20:02 ` [PATCH/RFT 3/5] " Rik van Riel
2005-08-10 20:02 ` Rik van Riel
2005-08-10 20:02 ` [PATCH/RFT 4/5] " Rik van Riel
2005-08-10 20:02 ` Rik van Riel
2005-08-10 20:31 ` David S. Miller
2005-08-10 20:31 ` David S. Miller, Rik van Riel
2005-08-18 0:38 ` Andrew Morton
2005-08-18 0:38 ` Andrew Morton
2005-08-18 2:48 ` David S. Miller
2005-08-18 2:48 ` David S. Miller, Andrew Morton
2005-08-18 4:05 ` Andrew Morton
2005-08-18 4:05 ` Andrew Morton
2005-08-18 4:48 ` David S. Miller
2005-08-18 4:48 ` David S. Miller, Andrew Morton
2005-08-19 7:03 ` Rusty Russell
2005-08-19 7:03 ` Rusty Russell
2005-08-19 7:10 ` Andrew Morton
2005-08-19 7:10 ` Andrew Morton
2005-08-19 7:27 ` Rusty Russell [this message]
2005-08-19 7:27 ` Rusty Russell
2005-08-19 13:04 ` Horst von Brand
2005-08-19 13:04 ` Horst von Brand
2005-08-10 23:22 ` Marcelo Tosatti
2005-08-10 23:22 ` Marcelo Tosatti
2005-08-11 0:06 ` Rik van Riel
2005-08-11 0:06 ` Rik van Riel
2005-08-10 20:02 ` [PATCH/RFT 5/5] " Rik van Riel
2005-08-10 20:02 ` Rik van Riel
2005-08-11 22:08 ` Song Jiang
2005-08-11 22:08 ` Song Jiang
2005-08-12 1:22 ` Rik van Riel
2005-08-12 1:22 ` Rik van Riel
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=1124436426.23757.5.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
/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.