All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Matthew Wilcox <willy@infradead.org>,
	Gao Xiang <xiang@kernel.org>,
	Jeffle Xu <jefflexu@linux.alibaba.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the folio tree
Date: Mon, 2 May 2022 18:01:20 +0800	[thread overview]
Message-ID: <Ym+r8OK3eWUihmr6@B-P7TQMD6M-0146.local> (raw)
In-Reply-To: <20220502180425.7305c335@canb.auug.org.au>

Hi Stephen,

On Mon, May 02, 2022 at 06:04:25PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the folio tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> fs/erofs/fscache.c:255:10: error: 'const struct address_space_operations' has no member named 'readpage'
>   255 |         .readpage = erofs_fscache_meta_readpage,
>       |          ^~~~~~~~
> fs/erofs/fscache.c:255:21: error: initialization of 'int (*)(struct page *, struct writeback_control *)' from incompatible pointer type 'int (*)(struct file *, struct page *)' [-Werror=incompatible-pointer-types]
>   255 |         .readpage = erofs_fscache_meta_readpage,
>       |                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~
> fs/erofs/fscache.c:255:21: note: (near initialization for 'erofs_fscache_meta_aops.writepage')
> fs/erofs/fscache.c:259:10: error: 'const struct address_space_operations' has no member named 'readpage'
>   259 |         .readpage = erofs_fscache_readpage,
>       |          ^~~~~~~~
> fs/erofs/fscache.c:259:21: error: initialization of 'int (*)(struct page *, struct writeback_control *)' from incompatible pointer type 'int (*)(struct file *, struct page *)' [-Werror=incompatible-pointer-types]
>   259 |         .readpage = erofs_fscache_readpage,
>       |                     ^~~~~~~~~~~~~~~~~~~~~~
> fs/erofs/fscache.c:259:21: note: (near initialization for 'erofs_fscache_access_aops.writepage')
> 
> Caused by commit
> 
>   00da6d4b7219 ("mm,fs: Remove stray references to ->readpage")
> 
> interacting with commits
> 
>   60aa7e805f00 ("erofs: implement fscache-based metadata read")
>   e472f468adbe ("erofs: implement fscache-based data read for non-inline layout")
> 
> from the erofs tree.
> 
> I have applied the following merge fix patch.
> 

That looks good to me, will point out this conflict then.

Thanks,
Gao Xiang

> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Mon, 2 May 2022 17:57:39 +1000
> Subject: [PATCH] fixup for "mm,fs: Remove stray references to ->readpage"
> 
> interacting with commits
> 
>   60aa7e805f00 ("erofs: implement fscache-based metadata read")
>   e472f468adbe ("erofs: implement fscache-based data read for non-inline layout")
> 
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
>  fs/erofs/fscache.c | 10 ++++------
>  1 file changed, 4 insertions(+), 6 deletions(-)
> 
> diff --git a/fs/erofs/fscache.c b/fs/erofs/fscache.c
> index a402d8f0a063..1bb2d0fc19c8 100644
> --- a/fs/erofs/fscache.c
> +++ b/fs/erofs/fscache.c
> @@ -59,10 +59,9 @@ static int erofs_fscache_read_folios(struct fscache_cookie *cookie,
>  	return ret;
>  }
>  
> -static int erofs_fscache_meta_readpage(struct file *data, struct page *page)
> +static int erofs_fscache_meta_read_folio(struct file *data, struct folio *folio)
>  {
>  	int ret;
> -	struct folio *folio = page_folio(page);
>  	struct super_block *sb = folio_mapping(folio)->host->i_sb;
>  	struct erofs_map_dev mdev = {
>  		.m_deviceid = 0,
> @@ -110,9 +109,8 @@ static int erofs_fscache_readpage_inline(struct folio *folio,
>  	return 0;
>  }
>  
> -static int erofs_fscache_readpage(struct file *file, struct page *page)
> +static int erofs_fscache_read_folio(struct file *file, struct folio *folio)
>  {
> -	struct folio *folio = page_folio(page);
>  	struct inode *inode = folio_mapping(folio)->host;
>  	struct super_block *sb = inode->i_sb;
>  	struct erofs_map_blocks map;
> @@ -252,11 +250,11 @@ static void erofs_fscache_readahead(struct readahead_control *rac)
>  }
>  
>  static const struct address_space_operations erofs_fscache_meta_aops = {
> -	.readpage = erofs_fscache_meta_readpage,
> +	.read_folio = erofs_fscache_meta_read_folio,
>  };
>  
>  const struct address_space_operations erofs_fscache_access_aops = {
> -	.readpage = erofs_fscache_readpage,
> +	.read_folio = erofs_fscache_read_folio,
>  	.readahead = erofs_fscache_readahead,
>  };
>  
> -- 
> 2.35.1
> 
> -- 
> Cheers,
> Stephen Rothwell



  reply	other threads:[~2022-05-02 10:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02  8:04 linux-next: build failure after merge of the folio tree Stephen Rothwell
2022-05-02 10:01 ` Gao Xiang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-15 10:26 Stephen Rothwell
2022-03-15 14:42 ` Matthew Wilcox
2022-02-28 12:53 Stephen Rothwell
2022-02-17  7:20 Stephen Rothwell
2022-02-15  6:44 Stephen Rothwell
2022-02-07  4:06 Stephen Rothwell
2022-02-09  3:38 ` Stephen Rothwell
2022-02-09  3:47   ` Matthew Wilcox
2022-01-04  7:29 Stephen Rothwell
2021-11-01  6:48 Stephen Rothwell
2021-09-21  4:26 Stephen Rothwell
2021-09-22  4:19 ` Stephen Rothwell
2021-11-01 22:05   ` Stephen Rothwell
2021-11-02  7:02   ` David Howells

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=Ym+r8OK3eWUihmr6@B-P7TQMD6M-0146.local \
    --to=hsiangkao@linux.alibaba.com \
    --cc=jefflexu@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=willy@infradead.org \
    --cc=xiang@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.