From: kernel test robot <lkp@intel.com>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
Christian Brauner <brauner@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs: Add uoff_t
Date: Wed, 19 Nov 2025 10:19:25 +0800 [thread overview]
Message-ID: <202511190917.pXdJRhD8-lkp@intel.com> (raw)
In-Reply-To: <20251118152935.3735484-1-willy@infradead.org>
Hi Matthew,
kernel test robot noticed the following build errors:
[auto build test ERROR on akpm-mm/mm-everything]
[also build test ERROR on arnd-asm-generic/master linus/master v6.18-rc6 next-20251118]
[cannot apply to brauner-vfs/vfs.all]
[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/Matthew-Wilcox-Oracle/fs-Add-uoff_t/20251118-233038
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/20251118152935.3735484-1-willy%40infradead.org
patch subject: [PATCH] fs: Add uoff_t
config: arm-allnoconfig (https://download.01.org/0day-ci/archive/20251119/202511190917.pXdJRhD8-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 0bba1e76581bad04e7d7f09f5115ae5e2989e0d9)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251119/202511190917.pXdJRhD8-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/202511190917.pXdJRhD8-lkp@intel.com/
All errors (new ones prefixed by >>):
>> mm/shmem.c:5810:6: error: conflicting types for 'shmem_truncate_range'
5810 | void shmem_truncate_range(struct inode *inode, loff_t lstart, loff_t lend)
| ^
include/linux/shmem_fs.h:129:6: note: previous declaration is here
129 | void shmem_truncate_range(struct inode *inode, loff_t start, uoff_t end);
| ^
mm/shmem.c:5838:16: warning: unused variable 'flags' [-Wunused-variable]
5838 | unsigned long flags = (vm_flags & VM_NORESERVE) ? SHMEM_F_NORESERVE : 0;
| ^~~~~
1 warning and 1 error generated.
vim +/shmem_truncate_range +5810 mm/shmem.c
c01d5b300774d13 Hugh Dickins 2016-07-26 5809
41ffe5d5ceef7f7 Hugh Dickins 2011-08-03 @5810 void shmem_truncate_range(struct inode *inode, loff_t lstart, loff_t lend)
94c1e62df4494b7 Hugh Dickins 2011-06-27 5811 {
41ffe5d5ceef7f7 Hugh Dickins 2011-08-03 5812 truncate_inode_pages_range(inode->i_mapping, lstart, lend);
94c1e62df4494b7 Hugh Dickins 2011-06-27 5813 }
94c1e62df4494b7 Hugh Dickins 2011-06-27 5814 EXPORT_SYMBOL_GPL(shmem_truncate_range);
94c1e62df4494b7 Hugh Dickins 2011-06-27 5815
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2025-11-19 2:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20251118152935.3735484-1-willy@infradead.org>]
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=202511190917.pXdJRhD8-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
--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).