From: "Oliver Pinter" <oliver.pntr@gmail.com>
To: "Pekka Enberg" <penberg@cs.helsinki.fi>
Cc: "Daniel Yeisley" <dan.yeisley@unisys.com>,
linux-kernel@vger.kernel.org, akpm@osdl.org,
"Christoph Lameter" <clameter@sgi.com>,
mel@csn.ul.ie
Subject: Re: [PATCH] list_add corruption in slab.c
Date: Tue, 25 Mar 2008 22:27:25 +0100 [thread overview]
Message-ID: <6101e8c40803251427t777b0afdlf9e49e36b193c729@mail.gmail.com> (raw)
In-Reply-To: <47E96B0A.2010906@cs.helsinki.fi>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1554 bytes --]
Hi Pekka
this patch for 2.6.22?(http://repo.or.cz/w/linux-2.6.22.y-op.git)
--8<-- /* 1) create the cache_cache */ INIT_LIST_HEAD(&cache_chain); list_add(&cache_cache.next, &cache_chain); cache_cache.colour_off = cache_line_size(); cache_cache.array[smp_processor_id()] = &initarray_cache.cache; cache_cache.nodelists[node] = &initkmem_list3[CACHE_CACHE];-->8--from 2.6.22's slab.c
On 3/25/08, Pekka Enberg <penberg@cs.helsinki.fi> wrote:> Hi Daniel,>> Daniel Yeisley wrote:> > I actually saw that initkmem_list reference, but didn't change it since> > my original patch fixed my list corruption. Anyway, I made the changed> > and tested it. The system booted fine.>> Yeah, but the second change is needed; otherwise we forget to fix up> some of the bootstrap caches.>> > Signed-off-by: Dan Yeisley <dan.yeisley@unisys.com>>> Reviewed-by: Pekka Enberg <penberg@cs.helsinki.fi>>> Mel, as this change is related to the memoryless node fix that went in> 2.6.24, any chance you'd give this patch a spin on your machines so we> can get the fix in 2.6.25 and 2.6.24-stable?>> Pekka> --> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in> the body of a message to majordomo@vger.kernel.org> More majordomo info at http://vger.kernel.org/majordomo-info.html> Please read the FAQ at http://www.tux.org/lkml/>
-- Thanks,Oliverÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2008-03-25 21:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 16:57 Daniel Yeisley
2008-03-25 18:45 ` Pekka Enberg
2008-03-25 20:44 ` Daniel Yeisley
2008-03-25 21:13 ` Pekka Enberg
2008-03-25 21:27 ` Oliver Pinter [this message]
2008-03-25 21:38 ` Pekka Enberg
2008-03-25 21:42 ` Oliver Pinter
2008-03-26 14:16 ` Mel Gorman
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=6101e8c40803251427t777b0afdlf9e49e36b193c729@mail.gmail.com \
--to=oliver.pntr@gmail.com \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=dan.yeisley@unisys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=penberg@cs.helsinki.fi \
/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®