Skip to contentSkip to conversation

linux-next: manual merge of the ext4 tree with the mm-stable tree

PATCH [email protected] 1 participant 1 message Apr 13, 2023

Subsystems (2)
Linux-next tree Page cache
lore
Share & tools
lore

[email protected]

author maintainer
#0 lore raw

Hi all,

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

include/linux/pagemap.h

between commit:

263e721e3ba1f ("mm: make mapping_get_entry available outside of filemap.c")

from the mm-stable tree and commit:

e999a5c5a19cf ("fs: Add FGP_WRITEBEGIN")

from the ext4 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.

include/linux/pagemap.h +0 -0
diff --cc include/linux/pagemap.h
index fdcd595d22944,51b75b89730ed..0000000000000
@@@ -504,9 -504,11 +504,11 @@@ pgoff_t page_cache_prev_miss(struct add
  #define FGP_NOFS		0x00000010
  #define FGP_NOWAIT		0x00000020
  #define FGP_FOR_MMAP		0x00000040
 -#define FGP_ENTRY		0x00000080
 -#define FGP_STABLE		0x00000100
 +#define FGP_STABLE		0x00000080
  
+ #define FGP_WRITEBEGIN		(FGP_LOCK | FGP_WRITE | FGP_CREAT | FGP_STABLE)
+ 
 +void *filemap_get_entry(struct address_space *mapping, pgoff_t index);
  struct folio *__filemap_get_folio(struct address_space *mapping, pgoff_t index,
  		int fgp_flags, gfp_t gfp);
  struct page *pagecache_get_page(struct address_space *mapping, pgoff_t index,