From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Matthew Wilcox <willy@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the folio tree
Date: Tue, 15 Feb 2022 17:44:11 +1100 [thread overview]
Message-ID: <20220215174411.49e1d3ba@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]
Hi all,
After merging the folio tree, today's linux-next build (sparc defconfig)
failed like this:
mm/page_vma_mapped.c: In function 'page_vma_mapped_walk':
mm/page_vma_mapped.c:219:48: error: implicit declaration of function 'pmd_pfn'; did you mean 'pmd_off'? [-Werror=implicit-function-declaration]
219 | if (!check_pmd(pmd_pfn(pmde), pvmw))
| ^~~~~~~
| pmd_off
Caused by commit
b1dede582893 ("mm: Convert page_vma_mapped_walk to work on PFNs")
I applied the following hack just to make it build:
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Tue, 15 Feb 2022 17:15:48 +1100
Subject: [PATCH] fix up for "mm: Convert page_vma_mapped_walk to work on PFNs"
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
arch/sparc/include/asm/pgtable_32.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/sparc/include/asm/pgtable_32.h b/arch/sparc/include/asm/pgtable_32.h
index ffccfe3b22ed..30d55a37515d 100644
--- a/arch/sparc/include/asm/pgtable_32.h
+++ b/arch/sparc/include/asm/pgtable_32.h
@@ -424,6 +424,13 @@ static inline int io_remap_pfn_range(struct vm_area_struct *vma,
__changed; \
})
+static inline unsigned long pmd_pfn(pmd_t pmd)
+{
+ pte_t pte = __pte(pmd_val(pmd));
+
+ return pte_pfn(pte);
+}
+
#endif /* !(__ASSEMBLY__) */
#define VMALLOC_START _AC(0xfe600000,UL)
--
2.34.1
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-02-15 6:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 6:44 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-02 8:04 linux-next: build failure after merge of the folio tree Stephen Rothwell
2022-05-02 10:01 ` Gao Xiang
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-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=20220215174411.49e1d3ba@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).