linux-kernel - Re: Build error for nommu if CONFIG_DEBUG_ATOMIC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131018141202.GA24660@redhat.com>
Date:	Fri, 18 Oct 2013 17:12:02 +0300
From:	"Michael S. Tsirkin" <mst@...hat.com>
To:	Axel Lin <axel.lin@...ics.com>
Cc:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: Build error for nommu if CONFIG_DEBUG_ATOMIC_SLEEP is selected

On Fri, Oct 18, 2013 at 05:27:55PM +0800, Axel Lin wrote:
> 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

Can you send/upload your full .config please?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/