From: kernel test robot <lkp@intel.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Isaku Yamahata <isaku.yamahata@intel.com>,
Chao Peng <chao.p.peng@linux.intel.com>
Subject: [intel-tdx:kvm-upstream-workaround 333/429] include/linux/memfile_notifier.h:93:13: error: 'memfile_unregister_notifier' defined but not used
Date: Fri, 27 May 2022 19:40:41 +0800 [thread overview]
Message-ID: <202205271946.aUffZ0Xh-lkp@intel.com> (raw)
tree: https://github.com/intel/tdx.git kvm-upstream-workaround
head: 49c277ae966b45577acad5c6d98acba3d27d63af
commit: a46fd36366f3a53f0ea7385cdddef7d5e373edd0 [333/429] mm/shmem: Support memfile_notifier
config: x86_64-defconfig (https://download.01.org/0day-ci/archive/20220527/202205271946.aUffZ0Xh-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-1) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/intel/tdx/commit/a46fd36366f3a53f0ea7385cdddef7d5e373edd0
git remote add intel-tdx https://github.com/intel/tdx.git
git fetch --no-tags intel-tdx kvm-upstream-workaround
git checkout a46fd36366f3a53f0ea7385cdddef7d5e373edd0
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from include/linux/shmem_fs.h:12,
from drivers/gpu/drm/i915/gt/shmem_utils.c:9:
include/linux/memfile_notifier.h:87:57: error: unknown type name 'flags'
87 | static int memfile_register_notifier(struct file *file, flags,
| ^~~~~
In file included from include/linux/shmem_fs.h:12,
from drivers/gpu/drm/i915/gt/shmem_utils.c:9:
>> include/linux/memfile_notifier.h:93:13: error: 'memfile_unregister_notifier' defined but not used [-Werror=unused-function]
93 | static void memfile_unregister_notifier(struct memfile_notifier *notifier)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
>> include/linux/memfile_notifier.h:82:13: error: 'memfile_notifier_invalidate' defined but not used [-Werror=unused-function]
82 | static void memfile_notifier_invalidate(struct memfile_node *node,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
>> include/linux/memfile_notifier.h:77:13: error: 'memfile_notifier_populate' defined but not used [-Werror=unused-function]
77 | static void memfile_notifier_populate(struct memfile_node *node,
| ^~~~~~~~~~~~~~~~~~~~~~~~~
>> include/linux/memfile_notifier.h:72:12: error: 'memfile_node_set_flags' defined but not used [-Werror=unused-function]
72 | static int memfile_node_set_flags(struct file *file, unsigned long flags)
| ^~~~~~~~~~~~~~~~~~~~~~
>> include/linux/memfile_notifier.h:68:13: error: 'memfile_register_backing_store' defined but not used [-Werror=unused-function]
68 | static void memfile_register_backing_store(struct memfile_backing_store *bs)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/memfile_unregister_notifier +93 include/linux/memfile_notifier.h
07b4263e3099f77 Chao Peng 2022-01-12 66
07b4263e3099f77 Chao Peng 2022-01-12 67 #else /* !CONFIG_MEMFILE_NOTIFIER */
07b4263e3099f77 Chao Peng 2022-01-12 @68 static void memfile_register_backing_store(struct memfile_backing_store *bs)
07b4263e3099f77 Chao Peng 2022-01-12 69 {
07b4263e3099f77 Chao Peng 2022-01-12 70 }
07b4263e3099f77 Chao Peng 2022-01-12 71
07b4263e3099f77 Chao Peng 2022-01-12 @72 static int memfile_node_set_flags(struct file *file, unsigned long flags)
07b4263e3099f77 Chao Peng 2022-01-12 73 {
07b4263e3099f77 Chao Peng 2022-01-12 74 return -EOPNOTSUPP;
07b4263e3099f77 Chao Peng 2022-01-12 75 }
07b4263e3099f77 Chao Peng 2022-01-12 76
07b4263e3099f77 Chao Peng 2022-01-12 @77 static void memfile_notifier_populate(struct memfile_node *node,
07b4263e3099f77 Chao Peng 2022-01-12 78 pgoff_t start, pgoff_t end)
07b4263e3099f77 Chao Peng 2022-01-12 79 {
07b4263e3099f77 Chao Peng 2022-01-12 80 }
07b4263e3099f77 Chao Peng 2022-01-12 81
07b4263e3099f77 Chao Peng 2022-01-12 @82 static void memfile_notifier_invalidate(struct memfile_node *node,
07b4263e3099f77 Chao Peng 2022-01-12 83 pgoff_t start, pgoff_t end)
07b4263e3099f77 Chao Peng 2022-01-12 84 {
07b4263e3099f77 Chao Peng 2022-01-12 85 }
07b4263e3099f77 Chao Peng 2022-01-12 86
07b4263e3099f77 Chao Peng 2022-01-12 87 static int memfile_register_notifier(struct file *file, flags,
07b4263e3099f77 Chao Peng 2022-01-12 88 struct memfile_notifier *notifier)
07b4263e3099f77 Chao Peng 2022-01-12 89 {
07b4263e3099f77 Chao Peng 2022-01-12 90 return -EOPNOTSUPP;
07b4263e3099f77 Chao Peng 2022-01-12 91 }
07b4263e3099f77 Chao Peng 2022-01-12 92
07b4263e3099f77 Chao Peng 2022-01-12 @93 static void memfile_unregister_notifier(struct memfile_notifier *notifier)
07b4263e3099f77 Chao Peng 2022-01-12 94 {
07b4263e3099f77 Chao Peng 2022-01-12 95 }
07b4263e3099f77 Chao Peng 2022-01-12 96
:::::: The code at line 93 was first introduced by commit
:::::: 07b4263e3099f776c35284155851f0e202b12a44 mm: Introduce memfile_notifier
:::::: TO: Chao Peng <chao.p.peng@linux.intel.com>
:::::: CC: Isaku Yamahata <isaku.yamahata@intel.com>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-27 11:44 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=202205271946.aUffZ0Xh-lkp@intel.com \
--to=lkp@intel.com \
--cc=chao.p.peng@linux.intel.com \
--cc=isaku.yamahata@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.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