From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
David Hildenbrand <david@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-new 417/421] fs/xfs/xfs_file.c:1977:36: error: incompatible type for argument 1 of 'daxdev_mapping_supported'
Date: Tue, 20 Jan 2026 11:00:52 +0000 [thread overview]
Message-ID: <b900b7e2-a297-4a2e-bfcc-aa3313db5f6f@lucifer.local> (raw)
In-Reply-To: <202601201209.cGuf98oB-lkp@intel.com>
On Tue, Jan 20, 2026 at 12:30:13PM +0800, kernel test robot wrote:
> Hi Lorenzo,
>
> FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
> head: e4348a62bb1acacafcdeb149c9363291fae08c0c
> commit: e3900da1b37f861133669d26ae02415f18fa71b9 [417/421] mm: update all remaining mmap_prepare users to use vma_flags_t
> config: parisc-randconfig-001-20260120 (https://download.01.org/0day-ci/archive/20260120/202601201209.cGuf98oB-lkp@intel.com/config)
> compiler: hppa-linux-gcc (GCC) 8.5.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260120/202601201209.cGuf98oB-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202601201209.cGuf98oB-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> fs/xfs/xfs_file.c: In function 'xfs_file_mmap_prepare':
> >> fs/xfs/xfs_file.c:1977:36: error: incompatible type for argument 1 of 'daxdev_mapping_supported'
> if (!daxdev_mapping_supported(desc->vma_flags, file_inode(file),
> ~~~~^~~~~~~~~~~
> In file included from fs/xfs/xfs_buf.h:14,
> from fs/xfs/xfs_linux.h:81,
> from fs/xfs/xfs.h:26,
> from fs/xfs/xfs_file.c:6:
> include/linux/dax.h:114:56: note: expected 'vm_flags_t' {aka 'long unsigned int'} but argument is of type 'vma_flags_t' {aka 'struct <anonymous>'}
> static inline bool daxdev_mapping_supported(vm_flags_t vm_flags,
> ~~~~~~~~~~~^~~~~~~~
>
>
> vim +/daxdev_mapping_supported +1977 fs/xfs/xfs_file.c
>
> 1964
> 1965 STATIC int
> 1966 xfs_file_mmap_prepare(
> 1967 struct vm_area_desc *desc)
> 1968 {
> 1969 struct file *file = desc->file;
> 1970 struct inode *inode = file_inode(file);
> 1971 struct xfs_buftarg *target = xfs_inode_buftarg(XFS_I(inode));
> 1972
> 1973 /*
> 1974 * We don't support synchronous mappings for non-DAX files and
> 1975 * for DAX files if underneath dax_device is not synchronous.
> 1976 */
> > 1977 if (!daxdev_mapping_supported(desc->vma_flags, file_inode(file),
> 1978 target->bt_daxdev))
Same deal as other report, will fix.
> 1979 return -EOPNOTSUPP;
> 1980
> 1981 file_accessed(file);
> 1982 desc->vm_ops = &xfs_file_vm_ops;
> 1983 if (IS_DAX(inode))
> 1984 vma_desc_set_flags(desc, VMA_HUGEPAGE_BIT);
> 1985 return 0;
> 1986 }
> 1987
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-01-20 11:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 4:30 kernel test robot
2026-01-20 11:00 ` Lorenzo Stoakes [this message]
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=b900b7e2-a297-4a2e-bfcc-aa3313db5f6f@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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