linux-kernel - Re: Linking failure on linux-next with arm allyesconfig

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>] [day] [month] [year] [list]

Message-ID: <20130822142339.GI6617@n2100.arm.linux.org.uk>
Date:	Thu, 22 Aug 2013 15:23:39 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Tushar Behera <tushar.behera@...aro.org>,
	linux-kernel@...r.kernel.org,
	Frederic Weisbecker <fweisbec@...hat.com>
Cc:	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Kevin Hilman <khilman@...aro.org>
Subject: Re: Linking failure on linux-next with arm allyesconfig

I'm not sure why you're sending this to ARM people as I don't believe we
are the ones responsible for this breakage, neither have we had any
visibility of this breakage coming up.

>From what I can see, the mainline state is that we reference user_exit
when CONTEXT_TRACKING is enabled, and kernel/context_tracking.c is
built also when this symbol is enabled, and that file provides
user_exit() and user_entry().

If these two functions have been removed without our knowledge, it is
because someone is not following correct procedure when making changes
to the kernel source.  Using grep to find users of the symbols that
they're removing for example, and copying those who may be affected by
those changes with the patch etc.

If you are going to be spending time running build tests and reporting
breakage, can you also please spend the time to diagnose the cause of
the breakage so you can target your reports a little better.  Thanks.

On Thu, Aug 22, 2013 at 07:38:15PM +0530, Tushar Behera wrote:
> Hi,
> 
> With ARCH=arm 'allyesconfig' on next-20130822, following linking error
> is observed.
> 
> arch/arm/kernel/built-in.o: In function `ret_fast_syscall':
> /home/tushar/work/lt_devel/staging-tree/linux-next/arch/arm/kernel/entry-common.S:42:
> undefined reference to `user_enter'
> arch/arm/kernel/built-in.o: In function `no_work_pending':
> /home/tushar/work/lt_devel/staging-tree/linux-next/arch/arm/kernel/entry-common.S:77:
> undefined reference to `user_enter'
> arch/arm/kernel/built-in.o: In function `vector_swi':
> /home/tushar/work/lt_devel/staging-tree/linux-next/arch/arm/kernel/entry-common.S:376:
> undefined reference to `user_exit'
> arch/arm/kernel/built-in.o: In function `__dabt_usr':
> /home/tushar/work/lt_devel/staging-tree/linux-next/arch/arm/kernel/entry-armv.S:365:
> undefined reference to `user_exit'
> arch/arm/kernel/built-in.o: In function `__irq_usr':
> /home/tushar/work/lt_devel/staging-tree/linux-next/arch/arm/kernel/entry-armv.S:375:
> undefined reference to `user_exit'
> arch/arm/kernel/built-in.o: In function `__und_usr':
> /home/tushar/work/lt_devel/staging-tree/linux-next/arch/arm/kernel/entry-armv.S:388:
> undefined reference to `user_exit'
> arch/arm/kernel/built-in.o: In function `__pabt_usr':
> /home/tushar/work/lt_devel/staging-tree/linux-next/arch/arm/kernel/entry-armv.S:662:
> undefined reference to `user_exit'
> 
> -- 
> Tushar Behera
--
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/