From: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public•gmane.org>
To: James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public•gmane.org>,
Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public•gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public•gmane.org
Cc: linux-next-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
Sachin Prabhu <sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public•gmane.org>,
David Howells <dhowells-H+wXaHxf7aLQT0dZR+AlfA@public•gmane.org>
Subject: Re: linux-next: build failure after merge of the security tree
Date: Fri, 20 May 2016 09:14:47 +1000 [thread overview]
Message-ID: <20160520091447.1cba4885@canb.auug.org.au> (raw)
In-Reply-To: <20160519140120.23b345a1-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
Hi Steve,
On Thu, 19 May 2016 14:01:20 +1000 Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public•gmane.org> 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 function 'keyring_alloc'
> keyring = keyring_alloc(".cifs_spnego",
> ^
> In file included from include/linux/cred.h:17:0,
> from include/linux/sched.h:56,
> from include/linux/kasan.h:4,
> from include/linux/slab.h:118,
> from fs/cifs/cifs_spnego.c:23:
> include/linux/key.h:302:20: note: declared here
> extern struct key *keyring_alloc(const char *description, kuid_t uid, kgid_t gid,
> ^
>
> Caused by commit
>
> 5b82c5cbcfe4 ("cifs: Create dedicated keyring for spnego operations")
>
> from the cifs tree interacting with commit
>
> 5ac7eace2d00 ("KEYS: Add a facility to restrict new links into a keyring")
>
> from the security tree.
>
> I added the following merge fix patch (and someone will have to let
> Linus know):
>
> From: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public•gmane.org>
> Date: Thu, 19 May 2016 13:45:10 +1000
> Subject: [PATCH] cifs: fix for keyringalloc() API change
>
> Signed-off-by: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public•gmane.org>
> ---
> fs/cifs/cifs_spnego.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/cifs/cifs_spnego.c b/fs/cifs/cifs_spnego.c
> index 248ab431930c..9ef0dfcb2f95 100644
> --- a/fs/cifs/cifs_spnego.c
> +++ b/fs/cifs/cifs_spnego.c
> @@ -207,7 +207,7 @@ init_cifs_spnego(void)
> GLOBAL_ROOT_UID, GLOBAL_ROOT_GID, cred,
> (KEY_POS_ALL & ~KEY_POS_SETATTR) |
> KEY_USR_VIEW | KEY_USR_READ,
> - KEY_ALLOC_NOT_IN_QUOTA, NULL);
> + KEY_ALLOC_NOT_IN_QUOTA, NULL, NULL);
> if (IS_ERR(keyring)) {
> ret = PTR_ERR(keyring);
> goto failed_put_cred;
> --
> 2.7.0
The security tree has now been merged into Linus' tree, so this build
breakage occurs when I merge the cifs tree. So you will need to tell
Linus about this needed fixup when he merges the cifs tree.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-05-19 23:14 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 4:01 linux-next: build failure after merge of the security tree Stephen Rothwell
[not found] ` <20160519140120.23b345a1-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2016-05-19 10:11 ` David Howells
2016-05-19 23:14 ` Stephen Rothwell [this message]
2016-05-20 3:07 ` Steve French
-- strict thread matches above, loose matches on Subject: below --
2026-06-02 16:16 Mark Brown
2026-06-02 16:31 ` Paul Moore
2026-06-02 16:52 ` Daniel Borkmann
2026-06-02 17:26 ` Paul Moore
2026-06-02 18:40 ` Paul Moore
2026-06-02 19:16 ` Mark Brown
2026-06-02 20:13 ` Paul Moore
2026-06-02 21:45 ` Paul Moore
2026-06-03 12:42 ` Mark Brown
2026-06-03 14:43 ` Paul Moore
2025-03-24 4:37 Stephen Rothwell
2025-02-10 1:18 Stephen Rothwell
2025-02-10 3:44 ` Paul Moore
2025-02-10 3:53 ` Stephen Rothwell
2025-02-10 14:51 ` Paul Moore
2020-07-08 4:00 Stephen Rothwell
2020-07-13 2:04 ` Stephen Rothwell
2020-07-13 2:06 ` Stephen Rothwell
2020-07-29 23:35 ` Stephen Rothwell
2020-07-30 2:35 ` James Morris
2020-07-30 2:59 ` Stephen Rothwell
2020-07-30 5:03 ` Stephen Rothwell
2020-08-04 3:36 ` James Morris
2019-08-12 4:58 Stephen Rothwell
2019-08-12 17:34 ` Kees Cook
2019-08-19 3:21 ` Stephen Rothwell
2019-08-19 3:38 ` Stephen Rothwell
2019-08-21 16:39 ` James Morris
2017-08-23 11:12 Stephen Rothwell
2017-08-17 2:51 Stephen Rothwell
2017-08-17 3:24 ` Kees Cook
2015-08-17 5:29 Stephen Rothwell
2015-08-17 6:04 ` Stephen Rothwell
2015-08-26 14:45 ` David Howells
2014-07-25 9:21 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160520091447.1cba4885@canb.auug.org.au \
--to=sfr-3fnu+uhb4dndw9hx6icosa@public$(echo .)gmane.org \
--cc=dhowells-H+wXaHxf7aLQT0dZR+AlfA@public$(echo .)gmane.org \
--cc=jmorris-gx6/JNMH7DfYtjvyW6yDsg@public$(echo .)gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public$(echo .)gmane.org \
--cc=sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public$(echo .)gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox