From: kernel test robot <lkp@intel.com>
To: Pavel Begunkov <asml.silence@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [isilence:syz/region-conversion-3 13/20] io_uring/memmap.c:386:12: warning: 'io_region_mmap' defined but not used
Date: Tue, 26 Nov 2024 10:38:56 +0800 [thread overview]
Message-ID: <202411261012.C28PcFox-lkp@intel.com> (raw)
tree: https://github.com/isilence/linux syz/region-conversion-3
head: eab28eddf62efd7e9a5d20b3b41e5943c9065e90
commit: 9d971641dc86981b9f6d12433fe55ed9d506ae32 [13/20] io_uring/memmap: implement mmap for regions
config: arm-vf610m4_defconfig (https://download.01.org/0day-ci/archive/20241126/202411261012.C28PcFox-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241126/202411261012.C28PcFox-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/202411261012.C28PcFox-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> io_uring/memmap.c:386:12: warning: 'io_region_mmap' defined but not used [-Wunused-function]
386 | static int io_region_mmap(struct io_ring_ctx *ctx,
| ^~~~~~~~~~~~~~
vim +/io_region_mmap +386 io_uring/memmap.c
385
> 386 static int io_region_mmap(struct io_ring_ctx *ctx,
387 struct io_mapped_region *mr,
388 struct vm_area_struct *vma)
389 {
390 unsigned long nr_pages = mr->nr_pages;
391
392 vm_flags_set(vma, VM_DONTEXPAND);
393 return vm_insert_pages(vma, vma->vm_start, mr->pages, &nr_pages);
394 }
395
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-11-26 2:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202411261012.C28PcFox-lkp@intel.com \
--to=lkp@intel.com \
--cc=asml.silence@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.