From: axel.lin@ingics.com (Axel Lin)
To: linux-arm-kernel@lists.infradead.org
Subject: Build error for nommu if CONFIG_DEBUG_ATOMIC_SLEEP is selected
Date: Fri, 18 Oct 2013 17:27:55 +0800 [thread overview]
Message-ID: <1382088475.16935.4.camel@phoenix> (raw)
Hi Michael,
I got below build error for nommu if CONFIG_DEBUG_ATOMIC_SLEEP is selected.
Also got the same build error if CONFIG_PROVE_LOCKING is selected.
Seems this issue is introduced by commit 662bbcb2747c2
"mm, sched: Allow uaccess in atomic with pagefault_disable()".
arch/arm/kernel/built-in.o: In function `arch_ptrace':
arch/arm/kernel/ptrace.c:852: undefined reference to `might_fault'
arch/arm/kernel/built-in.o: In function `restore_sigframe':
arch/arm/kernel/signal.c:173: undefined reference to `might_fault'
arch/arm/kernel/signal.c:174: undefined reference to `might_fault'
arch/arm/kernel/signal.c:175: undefined reference to `might_fault'
arch/arm/kernel/signal.c:176: undefined reference to `might_fault'
arch/arm/kernel/built-in.o:arch/arm/kernel/signal.c:177: more undefined references to `might_fault' follow
make: *** [vmlinux] Error 1
Regards,
Axel
WARNING: multiple messages have this Message-ID (diff)
From: Axel Lin <axel.lin@ingics.com>
To: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Build error for nommu if CONFIG_DEBUG_ATOMIC_SLEEP is selected
Date: Fri, 18 Oct 2013 17:27:55 +0800 [thread overview]
Message-ID: <1382088475.16935.4.camel@phoenix> (raw)
Hi Michael,
I got below build error for nommu if CONFIG_DEBUG_ATOMIC_SLEEP is selected.
Also got the same build error if CONFIG_PROVE_LOCKING is selected.
Seems this issue is introduced by commit 662bbcb2747c2
"mm, sched: Allow uaccess in atomic with pagefault_disable()".
arch/arm/kernel/built-in.o: In function `arch_ptrace':
arch/arm/kernel/ptrace.c:852: undefined reference to `might_fault'
arch/arm/kernel/built-in.o: In function `restore_sigframe':
arch/arm/kernel/signal.c:173: undefined reference to `might_fault'
arch/arm/kernel/signal.c:174: undefined reference to `might_fault'
arch/arm/kernel/signal.c:175: undefined reference to `might_fault'
arch/arm/kernel/signal.c:176: undefined reference to `might_fault'
arch/arm/kernel/built-in.o:arch/arm/kernel/signal.c:177: more undefined references to `might_fault' follow
make: *** [vmlinux] Error 1
Regards,
Axel
next reply other threads:[~2013-10-18 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 9:27 Axel Lin [this message]
2013-10-18 9:27 ` Build error for nommu if CONFIG_DEBUG_ATOMIC_SLEEP is selected Axel Lin
2013-10-18 14:12 ` Michael S. Tsirkin
2013-10-18 14:12 ` Michael S. Tsirkin
2013-10-18 14:21 ` Axel Lin
2013-10-18 14:21 ` Axel Lin
2013-10-18 15:30 ` Michael S. Tsirkin
2013-10-18 15:30 ` Michael S. Tsirkin
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=1382088475.16935.4.camel@phoenix \
--to=axel.lin@ingics.com \
--cc=linux-arm-kernel@lists.infradead.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 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.