Re: linux-next: build failure after merge of the security tree

On Thu, 30 Jul 2020, Stephen Rothwell wrote: > Hi James, > > On Thu, 30 Jul 2020 12:35:03 +1000 (AEST) James Morris > wrote: > > > > On Thu, 30 Jul 2020, Stephen Rothwell wrote: > > > > > > I am still applying the above patch ... > > > > > > The merge window is coming up fast ... is anythin

Re: linux-next: build failure after merge of the security tree

Hi Stephen, On Thu, 30 Jul 2020 12:59:04 +1000 Stephen Rothwell wrote: > > Hi James, > > On Thu, 30 Jul 2020 12:35:03 +1000 (AEST) James Morris > wrote: > > > > On Thu, 30 Jul 2020, Stephen Rothwell wrote: > > > > > > I am still applying the above patch ... > > > > > > The merge windo

Re: linux-next: build failure after merge of the security tree

Hi James, On Thu, 30 Jul 2020 12:35:03 +1000 (AEST) James Morris wrote: > > On Thu, 30 Jul 2020, Stephen Rothwell wrote: > > > > I am still applying the above patch ... > > > > The merge window is coming up fast ... is anything happening about this > > failure? > > A new patch is coming,

Re: linux-next: build failure after merge of the security tree

On Thu, 30 Jul 2020, Stephen Rothwell wrote: > > I am still applying the above patch ... > > The merge window is coming up fast ... is anything happening about this > failure? A new patch is coming, but I'm not sure this code has had enough review from the core VFS folk. Please drop secure_uff

Re: linux-next: build failure after merge of the security tree

Hi all, On Mon, 13 Jul 2020 12:04:19 +1000 Stephen Rothwell wrote: > > On Wed, 8 Jul 2020 14:00:34 +1000 Stephen Rothwell > wrote: > > > > After merging the security tree, today's linux-next build (powerpc > > ppc64_defconfig) failed like this: > > > > fs/anon_inodes.c: In function 'anon_inod

Re: linux-next: build failure after merge of the security tree

Hi all, On Mon, 13 Jul 2020 12:04:19 +1000 Stephen Rothwell wrote: > > I am still applying the above patch ... And the mail address Daniel Colascione bounces. -- Cheers, Stephen Rothwell pgp7yzn576n6Z.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the security tree

Hi all, On Wed, 8 Jul 2020 14:00:34 +1000 Stephen Rothwell wrote: > > After merging the security tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > fs/anon_inodes.c: In function 'anon_inode_make_secure_inode': > fs/anon_inodes.c:70:10: error: implicit declaration o

Re: linux-next: build failure after merge of the security tree

On Mon, 19 Aug 2019, Stephen Rothwell wrote: > > > 2.20.1 > > I am still applying that patch ... > Matthew folded it into commit e6b1db98cf4d54d9ea59cfcc195f70dc946fdd38. -- James Morris

Re: linux-next: build failure after merge of the security tree

Hi James, On Mon, 19 Aug 2019 13:21:19 +1000 Stephen Rothwell wrote: > > On Mon, 12 Aug 2019 10:34:17 -0700 Kees Cook wrote: > > > > On Mon, Aug 12, 2019 at 02:58:23PM +1000, Stephen Rothwell wrote: > > > > > > After merging the security tree, today's linux-next build (arm > > > multi_v7_def

Re: linux-next: build failure after merge of the security tree

Hi all, On Mon, 12 Aug 2019 10:34:17 -0700 Kees Cook wrote: > > On Mon, Aug 12, 2019 at 02:58:23PM +1000, Stephen Rothwell wrote: > > Hi all, > > > > After merging the security tree, today's linux-next build (arm > > multi_v7_defconfig) failed like below. > > > > Caused by commit > > > > 45d

Re: linux-next: build failure after merge of the security tree

On Mon, Aug 12, 2019 at 02:58:23PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the security tree, today's linux-next build (arm > multi_v7_defconfig) failed like below. > > Caused by commit > > 45d29f9e9b8b ("security: Support early LSMs") > > I have added the following fix for

Re: linux-next: build failure after merge of the security tree

On Wed, Aug 16, 2017 at 7:51 PM, Stephen Rothwell wrote: > Hi James, > > After merging the security tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > In file included from samples/seccomp/bpf-fancy.c:12:0: > samples/seccomp/bpf-fancy.c: In function 'main': > samples/secc

Re: linux-next: build failure after merge of the security tree

I fixed the build break (and some trivial compile warnings) due to the change to the format of keyring_alloc and repushed the *"cifs: Create dedicated keyring for spnego operations" patch to cifs-2.6.git for-next On Thu, May 19, 2016 at 6:14 PM, Stephen Rothwell wrote: > Hi Steve, > > On Thu, 19

Re: linux-next: build failure after merge of the security tree

Hi Steve, On Thu, 19 May 2016 14:01:20 +1000 Stephen Rothwell wrote: > > After merging the security tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > fs/cifs/cifs_spnego.c: In function 'init_cifs_spnego': > fs/cifs/cifs_spnego.c:206:12: error: too few arguments to fun

Re: linux-next: build failure after merge of the security tree

Stephen Rothwell wrote: > From: Stephen Rothwell > Date: Thu, 19 May 2016 13:45:10 +1000 > Subject: [PATCH] cifs: fix for keyringalloc() API change > > Signed-off-by: Stephen Rothwell > --- > fs/cifs/cifs_spnego.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/fs/ci

Re: linux-next: build failure after merge of the security tree

Stephen Rothwell wrote: > > After a bit of digging, I installed libssl-dev on my Debian build > > machines. > > Is this worth a mention in Documentation/Changes along with all the > other prerequisites? Could be. It's mentioned in the Kconfig and Documentation/module-signing.txt already, but t

Re: linux-next: build failure after merge of the security tree

Hi all, On Mon, 17 Aug 2015 15:29:53 +1000 Stephen Rothwell wrote: > > After a bit of digging, I installed libssl-dev on my Debian build > machines. Is this worth a mention in Documentation/Changes along with all the other prerequisites? -- Cheers, Stephen Rothwells...@can