From: "Liu, Yujie" <yujie.liu@intel.com>
To: lkp <lkp@intel.com>,
"oe-kbuild@lists.linux.dev" <oe-kbuild@lists.linux.dev>
Subject: RE: [agraf-2.6:kvm-kho-gmem-test 19/27] lib/kvm_util.c:202:46: warning: unused variable 'region'
Date: Mon, 6 May 2024 07:22:03 +0000 [thread overview]
Message-ID: <SA1PR11MB83937A1FC42881058E2F2487FB1C2@SA1PR11MB8393.namprd11.prod.outlook.com> (raw)
In-Reply-To: <202405050343.ZgfQxdbN-lkp@intel.com>
not_report
informal patch
XXX make fdbox work
-----Original Message-----
From: lkp <lkp@intel.com>
Sent: Sunday, May 5, 2024 03:28
To: oe-kbuild@lists.linux.dev
Cc: lkp <lkp@intel.com>
Subject: [agraf-2.6:kvm-kho-gmem-test 19/27] lib/kvm_util.c:202:46: warning: unused variable 'region'
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: kvm-ppc@vger.kernel.org
TO: Alexander Graf <graf@amazon.com>
tree: https://github.com/agraf/linux-2.6.git kvm-kho-gmem-test
head: 9a58862a298a63bad21d05191e28b857063bb9dc
commit: ea39f95803e6da8a46791922be3724b49bea2c7a [19/27] XXX make fdbox work
:::::: branch date: 35 hours ago
:::::: commit date: 7 weeks ago
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240505/202405050343.ZgfQxdbN-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/r/202405050343.ZgfQxdbN-lkp@intel.com/
All warnings (new ones prefixed by >>):
lib/kvm_util.c: In function 'vm_open':
>> lib/kvm_util.c:202:46: warning: unused variable 'region' [-Wunused-variable]
202 | struct userspace_mem_region *region;
| ^~~~~~
>> lib/kvm_util.c:201:36: warning: unused variable 'node' [-Wunused-variable]
201 | struct hlist_node *node;
| ^~~~
>> lib/kvm_util.c:200:21: warning: unused variable 'ctr' [-Wunused-variable]
200 | int ctr;
| ^~~
At top level:
cc1: note: unrecognized command-line option '-Wno-gnu-variable-sized-type-not-at-end' may have been intended to silence earlier diagnostics
vim +/region +202 tools/testing/selftests/kvm/lib/kvm_util.c
ea39f95803e6da Alexander Graf 2024-03-15 191
ccc82ba6bea451 Sean Christopherson 2022-02-14 192 static void vm_open(struct kvm_vm *vm)
fa3899add1056f Paolo Bonzini 2018-07-26 193 {
ccc82ba6bea451 Sean Christopherson 2022-02-14 194 vm->kvm_fd = _open_kvm_dev_path_or_exit(O_RDWR);
fa3899add1056f Paolo Bonzini 2018-07-26 195
7ed397d107d461 Sean Christopherson 2022-05-27 196 TEST_REQUIRE(kvm_has_cap(KVM_CAP_IMMEDIATE_EXIT));
c68c21ca929771 Paolo Bonzini 2019-04-11 197
ea39f95803e6da Alexander Graf 2024-03-15 198 /* XXX HACK! */
ea39f95803e6da Alexander Graf 2024-03-15 199 if (old_vmfd) {
ea39f95803e6da Alexander Graf 2024-03-15 200 int ctr;
ea39f95803e6da Alexander Graf 2024-03-15 201 struct hlist_node *node;
ea39f95803e6da Alexander Graf 2024-03-15 @202 struct userspace_mem_region *region;
ea39f95803e6da Alexander Graf 2024-03-15 203
ea39f95803e6da Alexander Graf 2024-03-15 204 /* Recover old VM fd */
ea39f95803e6da Alexander Graf 2024-03-15 205 vm->fd = old_vmfd;
ea39f95803e6da Alexander Graf 2024-03-15 206 } else
fcba483e824628 Sean Christopherson 2022-06-01 207 vm->fd = __kvm_ioctl(vm->kvm_fd, KVM_CREATE_VM, (void *)vm->type);
f9725f89dc5027 Sean Christopherson 2022-02-15 208 TEST_ASSERT(vm->fd >= 0, KVM_IOCTL_ERROR(KVM_CREATE_VM, vm->fd));
fa3899add1056f Paolo Bonzini 2018-07-26 209 }
fa3899add1056f Paolo Bonzini 2018-07-26 210
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-05-06 7:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-04 19:27 [agraf-2.6:kvm-kho-gmem-test 19/27] lib/kvm_util.c:202:46: warning: unused variable 'region' kernel test robot
2024-05-06 7:22 ` Liu, Yujie [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=SA1PR11MB83937A1FC42881058E2F2487FB1C2@SA1PR11MB8393.namprd11.prod.outlook.com \
--to=yujie.liu@intel.com \
--cc=lkp@intel.com \
--cc=oe-kbuild@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 read-only IMAP folder(s) and NNTP newsgroup(s).