public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Rob Landley <rob@landley.net>
Cc: Adrian Bunk <bunk@kernel.org>,
	linux-scsi@vger.kernel.org, sparclinux@vger.kernel.org,
	linux-kernel@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: Scsi on sparc build break in 2.6.23.
Date: Thu, 11 Oct 2007 08:30:38 -0500	[thread overview]
Message-ID: <1192109439.3352.11.camel@localhost.localdomain> (raw)
In-Reply-To: <200710110817.22344.rob@landley.net>

On Thu, 2007-10-11 at 08:17 -0500, Rob Landley wrote:
> On Thursday 11 October 2007 6:05:55 am Adrian Bunk wrote:
> > On Thu, Oct 11, 2007 at 05:52:48AM -0500, Rob Landley wrote:
> > > CONFIG_SCSI_SUNESP=y breaks the build in 2.6.23:
> > >
> > >   LD      vmlinux
> > > `scsi_esp_unregister' referenced in section `__ksymtab' of
> > > drivers/built-in.o: defined in discarded section `.exit.text' of
> > > drivers/built-in.o
> > > make: *** [vmlinux] Error 1
> > >
> > > Do you need my full .config to reproduce this?
> >
> > Please always attach the .config when reporting errors.
> > The few bytes don't matter and it often saves some time.
> >
> > I have an idea regarding what might be going wrong in this case,
> > but it would cost me additional time to look at it because you didn't
> > send your .config.
> 
> *shrug*  That's why I asked.
> 
> The reason I hesitated is I use miniconfig files rather than big .config 
> files, and some people get confused by that.  Drop the attached 
> miniconfig-linux in the kernel source directory and go:
>   make ARCH=sparc allnoconfig KCONFIG_ALLCONFIG=miniconfig-linux
> 
> That expands it to a big .config file, and from there "make ARCH=sparc 
> CROSS_COMPILE=sparc-" to reproduce the problem.  Assuming you have a sparc 
> cross-compiler lying around.
> 
> Disable CONFIG_SCSI_SUNESP and it builds to the end, (and the result boots but 
> won't mount the root filesystem, which is sort of expected).

This is a very subtle error.  You're building without hotplug, which
causes __devexit to become __exit, so scsi_esp_unregister is placed in
the discard section of vmlinux.  Unfortunately, the EXPORT_SYMBOL causes
it to be referenced from the symbol export table.

The fix is probably just to remove the __devexit tag from the function
rather than trying to work out how to make the export symbol conditional
on the symbol not being discarded.

James



  reply	other threads:[~2007-10-11 13:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11 10:52 Scsi on sparc build break in 2.6.23 Rob Landley
2007-10-11 11:05 ` Adrian Bunk
2007-10-11 13:17   ` Rob Landley
2007-10-11 13:30     ` James Bottomley [this message]
2007-10-11 15:35       ` [2.6 patch] esp_scsi.c: remove __dev{init,exit} Adrian Bunk
2007-10-11 22:47         ` Rob Landley
2007-10-11 21:49           ` David Miller
2007-10-18  8:18             ` Rob Landley
2007-10-11 15:21     ` Scsi on sparc build break in 2.6.23 Adrian Bunk
     [not found]       ` <200710111737.30420.rob@landley.net>
2007-10-11 23:56         ` Adrian Bunk
2007-10-12  0:10           ` Randy Dunlap
2007-10-13 19:09           ` Rob Landley
2007-10-13 19:26             ` Adrian Bunk

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=1192109439.3352.11.camel@localhost.localdomain \
    --to=james.bottomley@steeleye.com \
    --cc=bunk@kernel.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=sparclinux@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox