mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] jffs2: fix section mismatches
Date: Sat, 10 Jun 2006 16:29:45 -0700	[thread overview]
Message-ID: <20060610162945.b8823f6e.rdunlap@xenotime.net> (raw)
In-Reply-To: <1149976818.18635.153.camel@shinybook.infradead.org>

On Sat, 10 Jun 2006 23:00:17 +0100 David Woodhouse wrote:

> On Sat, 2006-06-10 at 13:28 -0700, Randy.Dunlap wrote:
> > Priority: not critical; makes init code discardable.
> > 
> > Fix section mismatch warnings:
> > WARNING: fs/jffs2/jffs2.o - Section mismatch: reference
> > to .init.text:jffs2_zlib_init from .text between
> > 'jffs2_compressors_init' (at offset 0x546) and
> > 'jffs2_compressors_exit' 
> 
> Some of this is already in -mm, isn't it?

Ack, one of them is, yes.  Sorry I missed it.

> I'm wary of this kind of change from drive-by patchers now -- I had to
> commit two fixes recently to remove __exit from functions which are
> actually called in the error case from the init function.

Surely those would have been caught with the modpost checker,
if the patch submitter(s) used it... ??
FWIW, I check the ones that I submit very carefully, but I too
can make mistakes.

> For those exit-and-error functions, I think we actually want an
> __initexit marker. In the built-in case, it can actually be discarded
> with the init code. In the modular case, it needs to be kept.

That sounds good, yes.

---
~Randy

  parent reply	other threads:[~2006-06-10 23:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-10 20:28 Randy.Dunlap
2006-06-10 22:00 ` David Woodhouse
2006-06-10 22:41   ` Sam Ravnborg
2006-06-10 23:29   ` Randy.Dunlap [this message]
2006-06-10 23:32     ` David Woodhouse

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=20060610162945.b8823f6e.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@osdl.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®