From: Hugh Dickins <hugh@veritas.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Russell King <rmk@arm.uk.linux.org>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] mm/swap_state.c: unexport swapper_space
Date: Sun, 6 Mar 2005 15:28:19 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.61.0503061515200.19898@goblin.wat.veritas.com> (raw)
In-Reply-To: <20050306144758.GJ5070@stusta.de>
On Sun, 6 Mar 2005, Adrian Bunk wrote:
> I didn't find any possible modular usage in the kernel.
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
> --- linux-2.6.11-mm1-full/mm/swap_state.c.old 2005-03-04 16:25:54.000000000 +0100
> +++ linux-2.6.11-mm1-full/mm/swap_state.c 2005-03-04 16:26:16.000000000 +0100
> @@ -40,7 +40,6 @@
> .i_mmap_nonlinear = LIST_HEAD_INIT(swapper_space.i_mmap_nonlinear),
> .backing_dev_info = &swap_backing_dev_info,
> };
> -EXPORT_SYMBOL(swapper_space);
>
> #define INC_CACHE_INFO(x) do { swap_cache_info.x++; } while (0)
I think this one should stay exported (or at least be re-exported
immediately on demand). It's used by the inline page_mapping() in
include/linux/mm.h, which _was_ used by various arch cacheflushing
inlines, which could reasonably be called from modular filesystems.
I think those architectures hit the missed export when the dependence
on &swapper_space got added to page_mapping(), the export was soon
added to mainline, but meanwhile they moved their inlines out-of-line
- perhaps temporarily, but not yet reverted.
Better leave it exported so long as page_mapping is using it.
Hugh
next prev parent reply other threads:[~2005-03-06 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 14:47 Adrian Bunk
2005-03-06 15:28 ` Hugh Dickins [this message]
2005-03-06 22:49 ` Christoph Hellwig
2005-03-08 9:09 ` Russell King
2005-03-08 11:45 ` Hugh Dickins
2005-03-25 1:11 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=Pine.LNX.4.61.0503061515200.19898@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.uk.linux.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®