linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	Christian Brauner <christian@brauner.io>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Andreas Gruenbacher <agruenba@redhat.com>,
	Jan Kara <jack@suse.com>,
	gfs2@lists.linux.dev, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gfs2, udf: update to use mmap_prepare
Date: Wed, 3 Sep 2025 16:13:42 +0800	[thread overview]
Message-ID: <202509031521.aEPzyTZp-lkp@intel.com> (raw)
In-Reply-To: <20250902115341.292100-1-lorenzo.stoakes@oracle.com>

Hi Lorenzo,

kernel test robot noticed the following build errors:

[auto build test ERROR on brauner-vfs/vfs.all]
[also build test ERROR on gfs2/for-next linus/master v6.17-rc4 next-20250902]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Lorenzo-Stoakes/gfs2-udf-update-to-use-mmap_prepare/20250902-200024
base:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all
patch link:    https://lore.kernel.org/r/20250902115341.292100-1-lorenzo.stoakes%40oracle.com
patch subject: [PATCH] gfs2, udf: update to use mmap_prepare
config: x86_64-randconfig-005-20250903 (https://download.01.org/0day-ci/archive/20250903/202509031521.aEPzyTZp-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250903/202509031521.aEPzyTZp-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/202509031521.aEPzyTZp-lkp@intel.com/

All errors (new ones prefixed by >>):

>> fs/gfs2/file.c:1582:18: error: use of undeclared identifier 'gfs2_mmap'; did you mean 'vfs_mmap'?
    1582 |         .mmap_prepare   = gfs2_mmap,
         |                           ^~~~~~~~~
         |                           vfs_mmap
   include/linux/fs.h:2393:19: note: 'vfs_mmap' declared here
    2393 | static inline int vfs_mmap(struct file *file, struct vm_area_struct *vma)
         |                   ^
>> fs/gfs2/file.c:1582:18: error: incompatible function pointer types initializing 'int (*)(struct vm_area_desc *)' with an expression of type 'int (struct file *, struct vm_area_struct *)' [-Wincompatible-function-pointer-types]
    1582 |         .mmap_prepare   = gfs2_mmap,
         |                           ^~~~~~~~~
   2 errors generated.


vim +1582 fs/gfs2/file.c

  1574	
  1575	const struct file_operations gfs2_file_fops = {
  1576		.llseek		= gfs2_llseek,
  1577		.read_iter	= gfs2_file_read_iter,
  1578		.write_iter	= gfs2_file_write_iter,
  1579		.iopoll		= iocb_bio_iopoll,
  1580		.unlocked_ioctl	= gfs2_ioctl,
  1581		.compat_ioctl	= gfs2_compat_ioctl,
> 1582		.mmap_prepare	= gfs2_mmap,
  1583		.open		= gfs2_open,
  1584		.release	= gfs2_release,
  1585		.fsync		= gfs2_fsync,
  1586		.lock		= gfs2_lock,
  1587		.flock		= gfs2_flock,
  1588		.splice_read	= copy_splice_read,
  1589		.splice_write	= gfs2_file_splice_write,
  1590		.setlease	= simple_nosetlease,
  1591		.fallocate	= gfs2_fallocate,
  1592		.fop_flags	= FOP_ASYNC_LOCK,
  1593	};
  1594	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2025-09-03  8:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02 11:53 [PATCH] gfs2, udf: update to use mmap_prepare Lorenzo Stoakes
2025-09-02 12:34 ` Andreas Gruenbacher
2025-09-02 12:38   ` Lorenzo Stoakes
2025-09-02 13:29 ` Jan Kara
2025-09-03  3:43 ` kernel test robot
2025-09-03 18:00   ` Lorenzo Stoakes
2025-09-03  8:13 ` kernel test robot [this message]
2025-09-03 13:35   ` Lorenzo Stoakes

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=202509031521.aEPzyTZp-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=agruenba@redhat.com \
    --cc=christian@brauner.io \
    --cc=gfs2@lists.linux.dev \
    --cc=jack@suse.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=lorenzo.stoakes@oracle.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;
as well as URLs for NNTP newsgroup(s).