From: Andi Kleen <ak@suse.de>
To: Ravikiran G Thirumalai <kiran@scalex86.org>
Cc: Eric Dumazet <dada1@cosmosbay.com>,
pravin shelar <pravins@calsoftinc.com>,
Shai Fultheim <shai@scalex86.org>,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] garbage values in file /proc/net/sockstat
Date: Thu, 26 Jan 2006 01:32:11 +0100 [thread overview]
Message-ID: <200601260132.12611.ak@suse.de> (raw)
In-Reply-To: <20060125195946.GC3573@localhost.localdomain>
On Wednesday 25 January 2006 20:59, Ravikiran G Thirumalai wrote:
> On Wed, Jan 25, 2006 at 02:31:15PM +0100, Andi Kleen wrote:
> > On Monday 23 January 2006 17:46, Eric Dumazet wrote:
> >
> > I think the best course of action for this now for 2.6.16 is:
> >
> > - mark percpu init data not __init
> > (this way it will still reference valid memory, although shared between
> > all impossible CPUs)
> > - keep the impossible CPUs per cpu data to point to the original reference
> > version (== offset 0)
> >
>
> How about doing the above using a debug config option? So that when the
> config option is turned on, all per-cpu area references to not possible
> cpus crash? and leave that option default on on -mm :)
In -mm* we could just apply Eric's patch and then someone should just
grep the tree for NR_CPUS and audit all users - that should
catch basically all occurrences. I can put it onto my todo list,
but I don't know when I'll get to it so it would be nice if someone
else could do this.
For 2.6.16 I think it's best to go forward with my hack.
> . That way we can
> quickly catch all references. We can probably change the arch independent
> setup_per_cpu_areas also to do allocations for cpu_possible cpus only while
> we are at it?
Eric did that already.
-Andi
next prev parent reply other threads:[~2006-01-26 0:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 11:21 [PATCH] garbage values in file /proc/net/sockstat pravin shelar
2006-01-23 11:24 ` Andi Kleen
2006-01-23 13:28 ` Eric Dumazet
2006-01-23 15:11 ` Andi Kleen
2006-01-23 16:28 ` Eric Dumazet
2006-01-23 16:46 ` Eric Dumazet
2006-01-25 13:31 ` Andi Kleen
2006-01-25 19:59 ` Ravikiran G Thirumalai
2006-01-25 20:47 ` Ravikiran G Thirumalai
2006-01-26 0:32 ` Andi Kleen [this message]
2006-01-25 21:45 ` Red zones (was: [PATCH] garbage values in file /proc/net/sockstat) Bernd Eckenfels
2006-01-26 5:28 ` Red zones Eric Dumazet
2006-01-26 10:07 ` Bernd Eckenfels
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=200601260132.12611.ak@suse.de \
--to=ak@suse.de \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pravins@calsoftinc.com \
--cc=shai@scalex86.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.