From: kernel test robot <lkp@intel.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, x86@kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: [tip:timers/vdso 33/41] arch/x86/entry/vdso/vma.c:199:3: warning: label followed by a declaration is a C23 extension
Date: Sat, 2 Nov 2024 23:39:02 +0800 [thread overview]
Message-ID: <202411022359.fBPFTg2T-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/vdso
head: a812eee0b68645e2916d4a4399280fe5471cac67
commit: e93d2521b27f0439872dfa4e4b92a9be6d73496f [33/41] x86/vdso: Split virtual clock pages into dedicated mapping
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20241102/202411022359.fBPFTg2T-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241102/202411022359.fBPFTg2T-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/202411022359.fBPFTg2T-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from arch/x86/entry/vdso/vma.c:7:
In file included from include/linux/mm.h:2213:
include/linux/vmstat.h:504:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion]
504 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~ ^
505 | item];
| ~~~~
include/linux/vmstat.h:511:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion]
511 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~ ^
512 | NR_VM_NUMA_EVENT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~~
include/linux/vmstat.h:518:36: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
518 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~~~~~~~~~ ^ ~~~
include/linux/vmstat.h:524:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion]
524 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~ ^
525 | NR_VM_NUMA_EVENT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~~
>> arch/x86/entry/vdso/vma.c:199:3: warning: label followed by a declaration is a C23 extension [-Wc23-extensions]
199 | struct pvclock_vsyscall_time_info *pvti =
| ^
arch/x86/entry/vdso/vma.c:209:3: warning: label followed by a declaration is a C23 extension [-Wc23-extensions]
209 | unsigned long pfn = hv_get_tsc_pfn();
| ^
6 warnings generated.
vim +199 arch/x86/entry/vdso/vma.c
192
193 static vm_fault_t vvar_vclock_fault(const struct vm_special_mapping *sm,
194 struct vm_area_struct *vma, struct vm_fault *vmf)
195 {
196 switch (vmf->pgoff) {
197 #ifdef CONFIG_PARAVIRT_CLOCK
198 case VDSO_PAGE_PVCLOCK_OFFSET:
> 199 struct pvclock_vsyscall_time_info *pvti =
200 pvclock_get_pvti_cpu0_va();
201 if (pvti && vclock_was_used(VDSO_CLOCKMODE_PVCLOCK))
202 return vmf_insert_pfn_prot(vma, vmf->address,
203 __pa(pvti) >> PAGE_SHIFT,
204 pgprot_decrypted(vma->vm_page_prot));
205 break;
206 #endif /* CONFIG_PARAVIRT_CLOCK */
207 #ifdef CONFIG_HYPERV_TIMER
208 case VDSO_PAGE_HVCLOCK_OFFSET:
209 unsigned long pfn = hv_get_tsc_pfn();
210
211 if (pfn && vclock_was_used(VDSO_CLOCKMODE_HVCLOCK))
212 return vmf_insert_pfn(vma, vmf->address, pfn);
213 break;
214 #endif /* CONFIG_HYPERV_TIMER */
215 }
216
217 return VM_FAULT_SIGBUS;
218 }
219
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-11-02 15: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=202411022359.fBPFTg2T-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=thomas.weissschuh@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®