From: Russell King <rmk@arm.linux.org.uk>
To: Soeren Sandmann Pedersen <sandmann@redhat.com>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: d451564 breakage
Date: Fri, 13 Nov 2009 15:11:19 +0000 [thread overview]
Message-ID: <20091113151119.GA27752@flint.arm.linux.org.uk> (raw)
Change:
highmem: Fix debug_kmap_atomic() to also handle KM_IRQ_PTE, KM_NMI, and KM_NMI_PTE
Appears to break ARM:
mm/highmem.c: In function ‘debug_kmap_atomic’:
mm/highmem.c:436: error: ‘KM_NMI’ undeclared (first use in this function)
mm/highmem.c:436: error: (Each undeclared identifier is reported only once
mm/highmem.c:436: error: for each function it appears in.)
mm/highmem.c:436: error: ‘KM_NMI_PTE’ undeclared (first use in this function)
mm/highmem.c:443: error: ‘KM_IRQ_PTE’ undeclared (first use in this function)
make[2]: *** [mm/highmem.o] Error 1
make[1]: *** [mm] Error 2
I'd prefer not to have to add these definitions just so that highmem
debugging can work for two reasons:
1. either we allocate mappings for these which will never be used, which
unnecessarily wastes precious virtual memory space.
2. we define them to be some other KM_* value and hope that they never
get used. If they do get used, we'll never know by way of compiler
error but could result in silent data corruption.
The only sane alternative I can see would be to define these as KM_TYPE_NR
and either ensure that kmap_atomic() always fails for out-of-bounds kmap
types (more preferable to catch problems but has a performance impact) or
we have the kmap debugging detect this as well.
Any preferences?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next reply other threads:[~2009-11-13 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 15:11 Russell King [this message]
2009-11-13 19:54 ` d451564 breakage Andrew Morton
2009-11-13 22:50 ` Ingo Molnar
2009-11-13 22:48 ` Ingo Molnar
2009-11-13 23:02 ` Russell King
2009-11-13 23:17 ` Ingo Molnar
2009-11-13 23:37 ` Russell King
2009-11-14 0:21 ` Ingo Molnar
2009-11-14 8:19 ` Russell King
2009-11-14 9:28 ` Ingo Molnar
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=20091113151119.GA27752@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sandmann@redhat.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