From: Mingming Cao <cmm@us.ibm.com>
To: Badari Pulavarty <pbadari@gmail.com>, Alex Tomas <alex@clusterfs.com>
Cc: Martin Michlmayr <tbm@cyrius.com>, ext4 <linux-ext4@vger.kernel.org>
Subject: Re: Fix section conflict of ext4_ext_{find_goal,invalidate_cache}
Date: Tue, 15 May 2007 11:59:08 -0700 [thread overview]
Message-ID: <1179255549.4819.7.camel@dyn9047017103.beaverton.ibm.com> (raw)
In-Reply-To: <1179252599.2836.127.camel@dyn9047017100.beaverton.ibm.com>
On Tue, 2007-05-15 at 11:09 -0700, Badari Pulavarty wrote:
> On Tue, 2007-05-15 at 19:15 +0200, Martin Michlmayr wrote:
> > Building with GCC 4.2, I get the following error:
> >
> > CC [M] fs/ext4/extents.o
> > fs/ext4/extents.c:2166: error: __ksymtab_ext4_ext_find_goal causes a section type conflict
> > fs/ext4/extents.c:2163: error: __ksymtab_ext4_ext_invalidate_cache causes a section type conflict
> >
> > This is because ext4_ext_find_goal and ext4_ext_invalidate_cache are
> > declared static but also exported.
>
> Hmm.. Why are these exported ?
> Looking at the code
>
>
> EXPORT_SYMBOL(ext4_ext_invalidate_cache);
> EXPORT_SYMBOL(ext4_ext_insert_extent);
> EXPORT_SYMBOL(ext4_ext_walk_space);
> EXPORT_SYMBOL(ext4_ext_find_goal);
> EXPORT_SYMBOL(ext4_ext_calc_credits_for_insert);
>
there is one more
EXPORT_SYMBOL(ext4_mark_inode_dirty);
And with fallocate() patch,
EXPORT_SYMBOL(ext4_fallocate);
> Mingming ? Why are we exporting these ?
>
Don't know. They should all used by ext4 only. Alex, can we remove these
exported symbols?
Mingming
next prev parent reply other threads:[~2007-05-15 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 17:15 Fix section conflict of ext4_ext_{find_goal,invalidate_cache} Martin Michlmayr
2007-05-15 18:09 ` Badari Pulavarty
2007-05-15 18:59 ` Mingming Cao [this message]
2007-05-15 19:06 ` Alex Tomas
2007-05-15 19:08 ` Alex Tomas
2007-05-15 20:43 ` [PATCH] Remove unnecessery exported ext4 symbols Mingming Cao
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=1179255549.4819.7.camel@dyn9047017103.beaverton.ibm.com \
--to=cmm@us.ibm.com \
--cc=alex@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=pbadari@gmail.com \
--cc=tbm@cyrius.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;
as well as URLs for NNTP newsgroup(s).