Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20221013101528.4afacfe3@canb.auug.org.au>
In-Reply-To: <20221013101528.4afacfe3@canb.auug.org.au>
From:   Miklos Szeredi <miklos@szeredi.hu>
Date:   Thu, 13 Oct 2022 10:49:50 +0200
Message-ID: <CAJfpegs85WbrJ8sQ5Y3XCwtSdSwjK+m5GCAkTBOEUBc1-=h0xg@mail.gmail.com>
Subject: Re: linux-next: build failure after merge of the fuse tree
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, 13 Oct 2022 at 01:15, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the fuse tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: modpost: ".delete_from_page_cache" [fs/fuse/fuse.ko] undefined!
>
> Caused by commit
>
>   0d659ac83481 ("fuse: fix readdir cache race")
>
> delete_from_page_cache has not been exported to modules since commit
>
>   452e9e6992fe ("filemap: Add filemap_remove_folio and __filemap_remove_folio")
>
> Which was merged into Linus tree in v5.17-rc1.
>
> I have used the fuse tree from next-20221012 for today.
>
> Is this really destined for v6.1?

This particular patch, yes.   I posted the patch and asked Willy about
delete_from_page_cache().

Rebased my for-next branch on HEAD and re-added the EXPORT_SYMBOL to
fix this for now.

Thanks,
Miklos