From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
linux-scsi@vger.kernel.org
Subject: Re: another SCSI sync
Date: Sat, 22 Feb 2003 20:41:36 +0000 [thread overview]
Message-ID: <20030222204136.A28427@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0302221225500.7635-100000@home.transmeta.com>; from torvalds@transmeta.com on Sat, Feb 22, 2003 at 12:34:46PM -0800
On Sat, Feb 22, 2003 at 12:34:46PM -0800, Linus Torvalds wrote:
> They are marked __exit, which means that they end up being marked unused
> _and_ in a segment that doesn't ever get loaded for built-in stuff (since
> clearly the built-in kernel can never unload).
>
> In general, it is just illegal to call an __exit function from something
> that isn't __exit itself. And these functions are called from __init
> function too.
>
> Please fix. In the meantime, my fix is to remove the two bogus "__exit"
> notifiers, and wondering to myself how the hell this ever worked for any
> of you guys.
Okay, this was my fault. It seems the old toolchain on SuSE 8.0
(gcc 2.95-based) doesn't seem to notice this yet. Your fix is correct,
there's no other fixups needed.
next prev parent reply other threads:[~2003-02-22 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1045932775.1946.18.camel@mulgrave>
2003-02-22 20:34 ` another SCSI sync Linus Torvalds
2003-02-22 20:41 ` Christoph Hellwig [this message]
[not found] <1046315953.1834.177.camel@mulgrave>
2003-03-05 15:58 ` Another SCSI Sync Linus Torvalds
2003-03-05 18:10 ` Mike Anderson
2003-03-05 19:01 ` Mike Anderson
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=20030222204136.A28427@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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