diff options
| author |   Tejun Heo <tj@kernel.org> | 2009-10-02 13:28:55 +0900 |
|---|---|---|
| committer | Tejun Heo <tj@kernel.org> | 2009-10-02 13:28:55 +0900 |
| commit | 126b3fcdecd350cad9700908d0ad845084e26a31 (patch) | |
| tree | 186a166e821bfb85b8434308c1577690aaa91ad4 /lib/spinlock_debug.c | |
| parent | Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable (diff) | |
| download | linux-rng-126b3fcdecd350cad9700908d0ad845084e26a31.tar.xz linux-rng-126b3fcdecd350cad9700908d0ad845084e26a31.zip | |
ia64: don't alias VMALLOC_END to vmalloc_end
If CONFIG_VIRTUAL_MEM_MAP is enabled, ia64 defines macro VMALLOC_END
as unsigned long variable vmalloc_end which is adjusted to prepare
room for vmemmap. This becomes probnlematic if a local variables
vmalloc_end is defined in some function (not very unlikely) and
VMALLOC_END is used in the function - the function thinks its
referencing the global VMALLOC_END value but would be referencing its
own local vmalloc_end variable.
There's no reason VMALLOC_END should be a macro. Just define it as an
unsigned long variable if CONFIG_VIRTUAL_MEM_MAP is set to avoid nasty
surprises.
Signed-off-by: Tejun Heo <tj@kernel.org>
Acked-by: Tony Luck <tony.luck@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>
Cc: linux-ia64 <linux-ia64@vger.kernel.org>
Cc: Christoph Lameter <cl@linux-foundation.org>
Diffstat (limited to 'lib/spinlock_debug.c')
0 files changed, 0 insertions, 0 deletions