From: Andi Kleen <ak@suse.de>
Organization: SUSE Linux Products GmbH, Nuernberg, GF: Markus Rex, HRB 16746 (AG Nuernberg)
To: Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] x86: fix section mismatch warnings in mtrr
Date: Sun, 27 May 2007 11:56:21 +0200
User-Agent: KMail/1.9.6
Cc: Indan Zupancic <indan@nul.nu>, Jeremy Fitzhardinge <jeremy@goop.org>,
       Andrey Borzenkov <arvidjaar@mail.ru>, linux-kernel@vger.kernel.org,
       Bernhard Walle <bwalle@suse.de>,
       Andrew Morton <akpm@linux-foundation.org>
References: <200705191443.27161.arvidjaar@mail.ru> <200705261802.08573.ak@suse.de> <20070527090542.GA18399@uranus.ravnborg.org>
In-Reply-To: <20070527090542.GA18399@uranus.ravnborg.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200705271156.22098.ak@suse.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 806
Lines: 21


> 
> So section mismatch warnings are more about catching sloopy usage of __init than it is to
> catch potential kernel oopesen. But the latter is a nice side effect that is appreciated.

My point was that I cannot recall a single real oops bug found by the compile
time checking.

We had a few in the past, but since we poison init data after boot they all tended
to be found quickly anyways.

But the warnings just seem to require endless changes and bogus changes
(randomly moving code which was actually ok because it only called 
in the init case).

-Andi
-
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/