linux-next: manual merge of the akpm-current tree with Linus' tree

From: Stephen Rothwell
Date: Wed Aug 15 2018 - 04:05:44 EST

Hi all,

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


between commits:

42e4089c7890 ("x86/speculation/l1tf: Disallow non privileged high MMIO PROT_NONE mappings")
6c26fcd2abfe ("x86/speculation/l1tf: Unbreak !__HAVE_ARCH_PFN_MODIFY_ALLOWED architectures")

from Linus' tree and commit:

c235da45bb89 ("mm: provide a fallback for PAGE_KERNEL_RO for architectures")

from the akpm-current 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/asm-generic/pgtable.h
index a75cb371cd19,81371468ed5a..000000000000
--- a/include/asm-generic/pgtable.h
+++ b/include/asm-generic/pgtable.h
@@@ -1083,18 -1083,24 +1083,36 @@@ int phys_mem_access_prot_allowed(struc
static inline void init_espfix_bsp(void) { }

+static inline bool pfn_modify_allowed(unsigned long pfn, pgprot_t prot)
+ return true;
+static inline bool arch_has_pfn_modify_check(void)
+ return false;
+ /*
+ * Architecture PAGE_KERNEL_* fallbacks
+ *
+ * Some architectures don't define certain PAGE_KERNEL_* flags. This is either
+ * because they really don't support them, or the port needs to be updated to
+ * reflect the required functionality. Below are a set of relatively safe
+ * fallbacks, as best effort, which we can count on in lieu of the architectures
+ * not defining them on their own yet.
+ */
+ #ifndef PAGE_KERNEL_RO
+ #endif
+ #endif
#endif /* !__ASSEMBLY__ */

#ifndef io_remap_pfn_range

Attachment: pgpiChx4BfRfF.pgp
Description: OpenPGP digital signature