From: Jens Axboe <jens.axboe@oracle.com>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fix section conflict of current_io_context
Date: Tue, 15 May 2007 19:24:49 +0200 [thread overview]
Message-ID: <20070515172448.GC23798@kernel.dk> (raw)
In-Reply-To: <20070515171540.GA20425@deprecation.cyrius.com>
On Tue, May 15 2007, Martin Michlmayr wrote:
> Building with GCC 4.2, I get the following error:
>
> CC block/ll_rw_blk.o
> block/ll_rw_blk.c:3751: error: __ksymtab_current_io_context causes a section type conflict
>
> This is because current_io_context is both declared static and exported.
>
> Signed-off-by: Martin Michlmayr <tbm@cyrius.com>
>
> --- a/block/ll_rw_blk.c
> +++ b/block/ll_rw_blk.c
> @@ -41,7 +41,7 @@ static void blk_unplug_timeout(unsigned long data);
> static void drive_stat_acct(struct request *rq, int nr_sectors, int new_io);
> static void init_request_from_bio(struct request *req, struct bio *bio);
> static int __make_request(request_queue_t *q, struct bio *bio);
> -static struct io_context *current_io_context(gfp_t gfp_flags, int node);
> +struct io_context *current_io_context(gfp_t gfp_flags, int node);
>
> /*
> * For the allocated request tables
> @@ -3723,7 +3723,7 @@ void exit_io_context(void)
> * but since the current task itself holds a reference, the context can be
> * used in general code, so long as it stays within `current` context.
> */
> -static struct io_context *current_io_context(gfp_t gfp_flags, int node)
> +struct io_context *current_io_context(gfp_t gfp_flags, int node)
> {
> struct task_struct *tsk = current;
> struct io_context *ret;
There are no users outside ll_rw_blk.c, so the export just needs to be
removed.
diff --git a/block/ll_rw_blk.c b/block/ll_rw_blk.c
index 1e853f4..b085d0e 100644
--- a/block/ll_rw_blk.c
+++ b/block/ll_rw_blk.c
@@ -3807,7 +3807,6 @@ static struct io_context *current_io_context(gfp_t gfp_flags, int node)
return ret;
}
-EXPORT_SYMBOL(current_io_context);
/*
* If the current task has no IO context then create one and initialise it.
--
Jens Axboe
prev parent reply other threads:[~2007-05-15 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 17:15 Fix section conflict of current_io_context Martin Michlmayr
2007-05-15 17:24 ` Jens Axboe [this message]
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=20070515172448.GC23798@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.