[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1d868a7a-0a15-e2b1-d73b-13d9229855ad@infradead.org>
Date: Wed, 26 Jun 2019 09:01:49 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
David Howells <dhowells@...hat.com>
Subject: Re: linux-next: Tree for Jun 26 (task_struct: cached_requested_key)
On 6/26/19 6:16 AM, Stephen Rothwell wrote:
> Hi all,
>
> The sparc64 builds are broken in this tree, sorry.
>
> Changes since 20190625:
>
>
> The keys tree gained conflicts aginst the ecryptfs and integrity trees.
Multiple build errors like this when CONFIG_KEYS is not set/enabled:
(this was seen on one i386 build)
# CONFIG_KEYS is not set
CONFIG_KEYS_REQUEST_CACHE=y
CC arch/x86/crypto/crc32-pclmul_glue.o
In file included from ../include/linux/export.h:45:0,
from ../include/linux/linkage.h:7,
from ../include/linux/kernel.h:8,
from ../arch/x86/entry/common.c:10:
../include/linux/tracehook.h: In function ‘tracehook_notify_resume’:
../include/linux/tracehook.h:191:22: error: ‘struct task_struct’ has no member named ‘cached_requested_key’
if (unlikely(current->cached_requested_key)) {
^
--
~Randy
Powered by blists - more mailing lists