From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Howells <dhowells@redhat.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mat Martineau <mathew.j.martineau@linux.intel.com>
Subject: linux-next: build failure after merge of the keys tree
Date: Tue, 4 Apr 2017 13:39:02 +1000 [thread overview]
Message-ID: <20170404133902.2c300679@canb.auug.org.au> (raw)
Hi David,
After merging the keys tree, today's linux-next build (x86_64
allmodconfig) failed like this:
security/integrity/digsig.c: In function 'integrity_init_keyring':
security/integrity/digsig.c:46:30: error: passing argument 7 of 'keyring_alloc' from incompatible pointer type [-Werror=incompatible-pointer-types]
#define restrict_link_to_ima restrict_link_by_builtin_and_secondary_trusted
^
security/integrity/digsig.c:95:9: note: in expansion of macro 'restrict_link_to_ima'
restrict_link_to_ima, NULL);
^
In file included from include/linux/cred.h:17:0,
from security/integrity/digsig.c:18:
include/linux/key.h:311:20: note: expected 'struct key_restriction *' but argument is of type 'int (*)(struct key *, const struct key_type *, const union key_payload *, struct key *)'
extern struct key *keyring_alloc(const char *description, kuid_t uid, kgid_t gid,
^
Caused by commits
aaf66c883813 ("KEYS: Split role of the keyring pointer for keyring restrict functions")
c5faca6b4a58 ("KEYS: Use structure to capture key restriction function and data")
I have used the version from next-20170403 for today.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-04-04 3:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 3:39 Stephen Rothwell [this message]
2017-11-13 2:08 linux-next: build failure after merge of the keys tree Stephen Rothwell
2017-11-13 11:21 ` David Howells
2019-08-16 5:04 Stephen Rothwell
2019-08-29 5:31 Stephen Rothwell
2019-09-02 6:19 ` Stephen Rothwell
2019-09-02 16:01 ` David Howells
2019-09-02 23:07 ` Stephen Rothwell
2019-09-02 23:21 ` Stephen Rothwell
2019-09-02 23:53 ` David Howells
2019-09-03 0:29 ` Stephen Rothwell
2019-09-02 23:20 ` David Howells
2019-09-02 23:39 ` Stephen Rothwell
2019-09-02 23:51 ` David Howells
2020-01-16 1:36 Stephen Rothwell
2020-02-09 23:05 Stephen Rothwell
2020-02-09 23:07 ` Stephen Rothwell
2020-02-11 23:23 ` Stephen Rothwell
2020-03-02 0:37 Stephen Rothwell
2020-03-02 15:23 ` Pavel Begunkov
2020-05-04 3:25 ` Stephen Rothwell
2020-05-04 3:29 ` Stephen Rothwell
2020-05-14 4:30 Stephen Rothwell
2020-05-14 4:46 ` Jason A. Donenfeld
2020-05-14 12:11 ` David Howells
2020-05-14 12:34 ` Masahiro Yamada
2020-05-14 23:25 ` Jason A. Donenfeld
2020-05-18 4:57 Stephen Rothwell
2020-12-11 4:50 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=20170404133902.2c300679@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).