LKML Archive on
 help / color / Atom feed
From: Stephen Rothwell <>
To: David Howells <>, James Morris <>
Cc: Linux Next Mailing List <>,
	Linux Kernel Mailing List <>,
	Matthew Garrett <>
Subject: linux-next: manual merge of the keys tree with the security tree
Date: Thu, 29 Aug 2019 15:06:09 +1000
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 2388 bytes --]

Hi all,

Today's linux-next merge of the keys tree got a conflict in:


between commit:

  9e47d31d6a57 ("security: Add a "locked down" LSM hook")

from the security tree and commit:

  25d2a1e61245 ("security: Add hooks to rule on setting a watch")

from the keys tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

Stephen Rothwell

diff --cc include/linux/security.h
index 23e1c3f17d48,003437714eee..000000000000
--- a/include/linux/security.h
+++ b/include/linux/security.h
@@@ -441,7 -394,13 +443,14 @@@ void security_inode_invalidate_secctx(s
  int security_inode_notifysecctx(struct inode *inode, void *ctx, u32 ctxlen);
  int security_inode_setsecctx(struct dentry *dentry, void *ctx, u32 ctxlen);
  int security_inode_getsecctx(struct inode *inode, void **ctx, u32 *ctxlen);
 +int security_locked_down(enum lockdown_reason what);
+ int security_watch_key(struct watch *watch, struct key *key);
+ int security_watch_devices(struct watch *watch);
+ int security_post_notification(const struct cred *w_cred,
+ 			       const struct cred *cred,
+ 			       struct watch_notification *n);
+ #endif /* CONFIG_WATCH_QUEUE */
  #else /* CONFIG_SECURITY */
  static inline int call_blocking_lsm_notifier(enum lsm_event event, void *data)
@@@ -1259,10 -1213,22 +1268,26 @@@ static inline int security_inode_getsec
  	return -EOPNOTSUPP;
 +static inline int security_locked_down(enum lockdown_reason what)
 +	return 0;
+ static inline int security_watch_key(struct watch *watch, struct key *key)
+ {
+ 	return 0;
+ }
+ static inline int security_watch_devices(struct watch *watch)
+ {
+ 	return 0;
+ }
+ static inline int security_post_notification(const struct cred *w_cred,
+ 					     const struct cred *cred,
+ 					     struct watch_notification *n)
+ {
+ 	return 0;
+ }
+ #endif /* CONFIG_WATCH_QUEUE */
  #endif	/* CONFIG_SECURITY */

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

LKML Archive on

Archives are clonable:
	git clone --mirror lkml/git/0.git
	git clone --mirror lkml/git/1.git
	git clone --mirror lkml/git/2.git
	git clone --mirror lkml/git/3.git
	git clone --mirror lkml/git/4.git
	git clone --mirror lkml/git/5.git
	git clone --mirror lkml/git/6.git
	git clone --mirror lkml/git/7.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 lkml lkml/ \
	public-inbox-index lkml

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone