From: Andrew Morton <akpm@linux-foundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
Puranjay Mohan <puranjay@kernel.org>,
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 mm-unstable tree
Date: Wed, 18 Mar 2026 11:20:01 -0700 [thread overview]
Message-ID: <20260318112001.d67d0e84a4d69b991f0f97f4@linux-foundation.org> (raw)
In-Reply-To: <abqtxbX0eW1Ljdhx@sirena.org.uk>
On Wed, 18 Mar 2026 13:51:01 +0000 Mark Brown <broonie@kernel.org> wrote:
> Hi all,
>
> After merging the mm-unstable tree, today's linux-next build
> (x86_64 allmodconfig rustfmtcheck) failed like this:
>
> Diff in /tmp/next/build/drivers/android/binder/page_range.rs:762:
> if let Some(unchecked_vma) = mmap_read.vma_lookup(vma_addr) {
> if let Some(vma) = check_vma(unchecked_vma, range_ptr) {
> let user_page_addr = vma_addr + (page_index << PAGE_SHIFT);
> - vma.zap_vma_range(user_page_addr, PAGE_SIZE);
> + vma.zap_vma_range(user_page_addr, PAGE_SIZE);
> }
> }
>
> Diff in /tmp/next/build/drivers/android/binder/page_range.rs:762:
> if let Some(unchecked_vma) = mmap_read.vma_lookup(vma_addr) {
> if let Some(vma) = check_vma(unchecked_vma, range_ptr) {
> let user_page_addr = vma_addr + (page_index << PAGE_SHIFT);
> - vma.zap_vma_range(user_page_addr, PAGE_SIZE);
> + vma.zap_vma_range(user_page_addr, PAGE_SIZE);
> }
> }
>
>
> Caused by commit
>
> 320e410f0294b (mm: rename zap_page_range_single() to zap_vma_range())
>
> I have used the tree from next-20260317 instead.
huh, is this python?
--- a/drivers/android/binder/page_range.rs~mm-rename-zap_page_range_single-to-zap_vma_range-fix
+++ a/drivers/android/binder/page_range.rs
@@ -762,7 +762,7 @@ unsafe extern "C" fn rust_shrink_free_pa
if let Some(unchecked_vma) = mmap_read.vma_lookup(vma_addr) {
if let Some(vma) = check_vma(unchecked_vma, range_ptr) {
let user_page_addr = vma_addr + (page_index << PAGE_SHIFT);
- vma.zap_vma_range(user_page_addr, PAGE_SIZE);
+ vma.zap_vma_range(user_page_addr, PAGE_SIZE);
}
}
_
next prev parent reply other threads:[~2026-03-18 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 13:51 linux-next: build failure after merge of the mm-unstable tree Mark Brown
2026-03-18 18:20 ` Andrew Morton [this message]
2026-03-18 19:08 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2026-01-07 0:16 Stephen Rothwell
2025-09-11 6:05 Stephen Rothwell
2025-09-11 7:44 ` Kairui Song
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=20260318112001.d67d0e84a4d69b991f0f97f4@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=puranjay@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox