From: David Woodhouse <dwmw2@infradead.org>
To: Mark Fortescue <mark@mtfhpc.demon.co.uk>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
sparclinux@vger.kernel.org, David Miller <davem@davemloft.net>,
Christoph Lameter <clameter@engr.sgi.com>,
William Lee Irwin III <wli@holomorphy.com>
Subject: Re: [PATCH] Re: Sparc32: random invalid instruction occourances on sparc32 (sun4c)
Date: Tue, 03 Jul 2007 23:33:25 -0400 [thread overview]
Message-ID: <1183520006.29081.79.camel@shinybook.infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0707040335230.30946@mtfhpc.demon.co.uk>
On Wed, 2007-07-04 at 04:27 +0100, Mark Fortescue wrote:
> I tried the previous patch and it looks like it fixes the issue however
> one of the test builds I did caused depmod to use up all available memory
> (40M - kernel memory) before taking out the kernel with the oom killer.
> At present, I do not know if it is a depmod issue or a kernel issue.
> I will have to do some more tests later on to day.
That's almost certain to be an unrelated issue.
> I have looked at the latest patch below and am I am still not sure about
> two areas. Please take a look at my offering based on your latest
> patch (included here to it will probably get mangled).
>
> Note the change to lines 2178 to 2185. I have also changed/moved the
> alignment of size (see lines 2197 to 2206) based on your changes.
The first looks correct; well spotted. The second is just cosmetic but
also seems correct. I might be inclined to make the #define
'RED_ZONE_ALIGN' and use it in the other places too.
--
dwmw2
next prev parent reply other threads:[~2007-07-04 3:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 16:45 [1/2] 2.6.22-rc7: known regressions Michal Piotrowski
2007-07-03 17:29 ` Sparc32: random invalid instruction occourances on sparc32 (sun4c) Mark Fortescue
2007-07-03 18:57 ` [PATCH] " Mark Fortescue
2007-07-03 19:26 ` David Woodhouse
2007-07-03 21:25 ` Mark Fortescue
2007-07-03 21:56 ` David Woodhouse
2007-07-03 22:47 ` Mark Fortescue
2007-07-03 23:36 ` David Woodhouse
2007-07-04 3:27 ` Mark Fortescue
2007-07-04 3:33 ` David Woodhouse [this message]
2007-07-04 10:27 ` Mark Fortescue
2007-07-04 14:46 ` David Woodhouse
2007-07-04 18:38 ` Mark Fortescue
2007-07-03 21:41 ` David Miller
2007-07-03 22:01 ` David Woodhouse
2007-07-03 17:50 ` [1/2] 2.6.22-rc7: known regressions Bartlomiej Zolnierkiewicz
2007-07-03 23:09 ` David Chinner
2007-07-05 0:20 ` David Woodhouse
2007-07-05 1:26 ` [PATCH 2.6.22 REGRESSION] Fix slab redzone alignment David Woodhouse
2007-07-05 1:42 ` [1/2] 2.6.22-rc7: known regressions David Woodhouse
2007-07-05 16:28 ` Linus Torvalds
2007-07-05 16:43 ` David Woodhouse
2007-07-05 18:46 ` David Woodhouse
2007-07-05 19:31 ` David Woodhouse
2007-07-05 19:51 ` Linus Torvalds
2007-07-05 21:03 ` Dmitry Torokhov
2007-07-06 22:50 ` Jiri Kosina
2007-07-07 0:33 ` Dmitry Torokhov
2007-07-07 1:05 ` Jiri Kosina
2007-07-07 1:28 ` David Woodhouse
2007-07-07 2:25 ` David Woodhouse
2007-07-07 18:28 ` Marcel Holtmann
2007-07-07 18:36 ` Linus Torvalds
2007-07-07 18:58 ` [PATCH] Fix use-after-free oops in Bluetooth HID David Woodhouse
2007-07-07 19:27 ` Linus Torvalds
2007-07-09 2:32 ` Dmitry Torokhov
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=1183520006.29081.79.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=clameter@engr.sgi.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark@mtfhpc.demon.co.uk \
--cc=sparclinux@vger.kernel.org \
--cc=wli@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®