From: Andi Kleen <ak@suse.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux arch <linux-arch@vger.kernel.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Are Section mismatches out of control?
Date: Fri, 1 Feb 2008 12:10:52 +0100 [thread overview]
Message-ID: <200802011210.52655.ak@suse.de> (raw)
In-Reply-To: <20080201104718.GA11717@uranus.ravnborg.org>
On Friday 01 February 2008 11:47:18 Sam Ravnborg wrote:
> James said in a related posting that the Section mismatch
> warnings were getting out of control.
My question is: where are crashes? If the sections were
really in such bad shape and since we poison (and sometimes
even unmap) init after boot we should in theory see a lot
of oops reports from this if there were really accesses to
them after boot.
Where are they?
> The total figure for this build is 106 warnings.
The interesting question is how many true bugs are in these warnings.
-Andi
next prev parent reply other threads:[~2008-02-01 11:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 10:47 Are Section mismatches out of control? Sam Ravnborg
2008-02-01 11:03 ` Andrew Morton
2008-02-01 11:21 ` Harvey Harrison
2008-02-01 13:30 ` Geert Uytterhoeven
2008-02-01 13:40 ` Sam Ravnborg
2008-02-01 21:22 ` Geert Uytterhoeven
2008-02-01 22:32 ` Sam Ravnborg
2008-02-02 16:42 ` Geert Uytterhoeven
2008-02-02 17:40 ` Sam Ravnborg
2008-02-01 17:02 ` Roland Dreier
2008-02-01 21:47 ` Jan Engelhardt
2008-02-01 22:10 ` James Bottomley
2008-02-01 22:40 ` Sam Ravnborg
2008-02-02 0:01 ` Jan Engelhardt
2008-02-01 14:48 ` Johannes Weiner
2008-02-01 15:00 ` James Bottomley
2008-02-01 16:43 ` Jeff Garzik
2008-02-01 20:17 ` Sam Ravnborg
2008-02-01 20:24 ` Jeff Garzik
2008-02-01 22:38 ` Sam Ravnborg
2008-02-01 11:10 ` Andi Kleen [this message]
2008-02-01 21:51 ` Jan Engelhardt
2008-02-02 4:12 ` Andi Kleen
2008-02-01 14:53 ` James Bottomley
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=200802011210.52655.ak@suse.de \
--to=ak@suse.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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.