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

From: [email-masked]
Date: Thu, 13 Apr 2023 15:55:15 +0100

Hi all,

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

  fs/iomap/buffered-io.c

between commit:

  66dabbb65d673 ("mm: return an ERR_PTR from __filemap_get_folio")

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.

diff --cc fs/iomap/buffered-io.c
index 96bb56c203f49,10a2035155835..0000000000000
--- a/fs/iomap/buffered-io.c
+++ b/fs/iomap/buffered-io.c
@@@ -467,7 -467,8 +467,7 @@@ EXPORT_SYMBOL_GPL(iomap_is_partially_up
   */
  struct folio *iomap_get_folio(struct iomap_iter *iter, loff_t pos)
  {
- 	unsigned fgp = FGP_LOCK | FGP_WRITE | FGP_CREAT | FGP_STABLE | FGP_NOFS;
+ 	unsigned fgp = FGP_WRITEBEGIN | FGP_NOFS;
 -	struct folio *folio;
  
  	if (iter->flags & IOMAP_NOWAIT)
  		fgp |= FGP_NOWAIT;