linux-kernel - Re: [PATCH] xen: fix building on ARM with CONFIG_HIBERNATE

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

Date:	Tue, 19 May 2015 16:15:13 +0100
From:	David Vrabel <david.vrabel@...rix.com>
To:	Boris Ostrovsky <boris.ostrovsky@...cle.com>,
	Arnd Bergmann <arnd@...db.de>
CC:	Stefano Stabellini <stefano.stabellini@...citrix.com>,
	<xen-devel@...ts.xenproject.org>,
	<linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] xen: fix building on ARM with CONFIG_HIBERNATE_CALLBACKS

On 19/05/15 15:49, Boris Ostrovsky wrote:
> On 05/19/2015 10:36 AM, Arnd Bergmann wrote:
>> On Tuesday 19 May 2015 09:57:19 Boris Ostrovsky wrote:
>>> On 05/19/2015 08:58 AM, Arnd Bergmann wrote:
>>>> A recent bug fix for x86 broke Xen on ARM for the case that
>>>> CONFIG_HIBERNATE_CALLBACKS is enabled:
>>>>
>>>> drivers/built-in.o: In function `do_suspend':
>>>> /git/arm-soc/drivers/xen/manage.c:134: undefined reference to
>>>> `xen_arch_suspend'
>>>> drivers/built-in.o:(.debug_addr+0xc3f4): undefined reference to
>>>> `xen_arch_suspend'
>>>>
>>>> It is not clear to me what needs to be done here, but this
>>>> patch avoids the build error by adding a stub for the
>>>> missing function.
>>> This is already fixed in Xen staging tree.
>> I see. Any chance to get that fix into linux-next soon?
> 
> 
> David, are you going to send pull request to Linus before rc5?

Yes.

David
--
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/