public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: Lorenzo Stoakes <ljs@kernel.org>,
	David Hildenbrand <david@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	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 fs-next tree
Date: Mon, 9 Mar 2026 14:29:35 +0000	[thread overview]
Message-ID: <aa7ZT-cQMVdQOOAj@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1748 bytes --]

Hi all,

After merging the fs-next tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

/tmp/next/build/fs/ntfs/file.c: In function 'ntfs_file_mmap_prepare':
/tmp/next/build/fs/ntfs/file.c:657:13: error: implicit declaration of function 'vma_desc_test_flags'; did you mean 'vma_desc_set_flags'? [-Wimplicit-function-declaration]
  657 |         if (vma_desc_test_flags(desc, VMA_WRITE_BIT)) {
      |             ^~~~~~~~~~~~~~~~~~~
      |             vma_desc_set_flags

Caused by an interaction with commit:

  2c3b5ea7028fa (mm: reintroduce vma_desc_test() as a singular flag test)

from one of the mm trees, I've fixed it up as below and can carry as
needed.

commit 8cbd256f4ac9d0b08b6fc30b305cfcb51b9de9f7
Author: Mark Brown <broonie@kernel.org>
Date:   Mon Mar 9 13:24:55 2026 +0000

    ntfs: Fix up mm merge
    
    /tmp/next/build/fs/ntfs/file.c: In function 'ntfs_file_mmap_prepare':
    /tmp/next/build/fs/ntfs/file.c:657:13: error: implicit declaration of function 'vma_desc_test_flags'; did you mean 'vma_desc_set_flags'? [-Wimplicit-function-declaration]
      657 |         if (vma_desc_test_flags(desc, VMA_WRITE_BIT)) {
          |             ^~~~~~~~~~~~~~~~~~~
    
    Signed-off-by: Mark Brown <broonie@kernel.org>

diff --git a/fs/ntfs/file.c b/fs/ntfs/file.c
index 2735780159999..e5b897a6c1e15 100644
--- a/fs/ntfs/file.c
+++ b/fs/ntfs/file.c
@@ -654,7 +654,7 @@ static int ntfs_file_mmap_prepare(struct vm_area_desc *desc)
 	if (NInoCompressed(NTFS_I(inode)))
 		return -EOPNOTSUPP;
 
-	if (vma_desc_test_flags(desc, VMA_WRITE_BIT)) {
+	if (vma_desc_test(desc, VMA_WRITE_BIT)) {
 		struct inode *inode = file_inode(file);
 		loff_t from, to;
 		int err;

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2026-03-09 14:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 14:29 Mark Brown [this message]
2026-03-09 23:08 ` linux-next: build failure after merge of the fs-next tree Namjae Jeon
2026-03-10  7:21   ` Lorenzo Stoakes (Oracle)
  -- strict thread matches above, loose matches on Subject: below --
2026-03-27 19:22 Mark Brown
2026-03-27 19:27 ` Lorenzo Stoakes (Oracle)
2026-03-28  1:16 ` Namjae Jeon

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=aa7ZT-cQMVdQOOAj@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=linkinjeon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ljs@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