From: Con Kolivas <kernel@kolivas.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Subject: Re: gcc 4.1.1 issues with 2.6.17-rc5
Date: Mon, 29 May 2006 14:52:25 +1000
User-Agent: KMail/1.9.1
Cc: rdunlap@xenotime.net, linux-kernel@vger.kernel.org, sam@ravnborg.org
References: <200605281255.49821.kernel@kolivas.org> <20060527223945.05cd5b5b.rdunlap@xenotime.net> <20060529.013226.108739444.anemo@mba.ocn.ne.jp>
In-Reply-To: <20060529.013226.108739444.anemo@mba.ocn.ne.jp>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200605291452.26423.kernel@kolivas.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1089
Lines: 29

On Monday 29 May 2006 02:32, Atsushi Nemoto wrote:
> On Sat, 27 May 2006 22:39:45 -0700, "Randy.Dunlap" <rdunlap@xenotime.net> 
wrote:
> > > and a missed one:
> > > WARNING: drivers/usb/storage/usb-storage.o - Section mismatch:
> > > reference to .exit.text: from .smp_locks after '' (at offset 0x40)
> >
> > Yep, Jesper posted that one.
> > I also see it in ieee1394.o.
> >
> > So where does the .smp_locks section come from?
> > Is this just a section checker bug/issue?
>
> The .smp_locks section comes from LOCK_PREFIX on x86.  I think the
> warnings was not shown previously just because the modpost did not
> check SHT_REL sections.
>
> Maybe we should fix the modpost to ignore it, but I'm not sure.  Is it
> really safe to ignore?  I'm not a x86 expert ...

A "scary but harmless" comment from someone in the know would be nice.

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