Re: [PATCH v3 2/2] cxl/core: add poison creation event handler
Hi Shiyang, kernel test robot noticed the following build errors: [auto build test ERROR on cxl/next] [also build test ERROR on linus/master v6.9-rc4 next-20240419] [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/Shiyang-Ruan/cxl-core-correct-length-of-DPA-field-masks/20240417-155443 base: https://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl.git next patch link: https://lore.kernel.org/r/20240417075053.3273543-3-ruansy.fnst%40fujitsu.com patch subject: [PATCH v3 2/2] cxl/core: add poison creation event handler config: csky-randconfig-002-20240421 (https://download.01.org/0day-ci/archive/20240421/202404212044.usxtgrtl-...@intel.com/config) compiler: csky-linux-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240421/202404212044.usxtgrtl-...@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 | Closes: https://lore.kernel.org/oe-kbuild-all/202404212044.usxtgrtl-...@intel.com/ All errors (new ones prefixed by >>): `.exit.text' referenced in section `__jump_table' of fs/ceph/super.o: defined in discarded section `.exit.text' of fs/ceph/super.o `.exit.text' referenced in section `__jump_table' of fs/ceph/super.o: defined in discarded section `.exit.text' of fs/ceph/super.o csky-linux-ld: drivers/cxl/core/mbox.o: in function `__cxl_report_poison': mbox.c:(.text+0xa12): undefined reference to `cxl_trace_hpa' >> csky-linux-ld: mbox.c:(.text+0xa44): undefined reference to `cxl_trace_hpa' `.exit.text' referenced in section `__jump_table' of drivers/target/target_core_configfs.o: defined in discarded section `.exit.text' of drivers/target/target_core_configfs.o `.exit.text' referenced in section `__jump_table' of drivers/target/target_core_configfs.o: defined in discarded section `.exit.text' of drivers/target/target_core_configfs.o `.exit.text' referenced in section `__jump_table' of net/ceph/ceph_common.o: defined in discarded section `.exit.text' of net/ceph/ceph_common.o `.exit.text' referenced in section `__jump_table' of net/ceph/ceph_common.o: defined in discarded section `.exit.text' of net/ceph/ceph_common.o -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH 3/3] virtio_balloon: Introduce memory recover
Hi zhenwei, Thank you for the patch! Yet something to improve: [auto build test ERROR on akpm-mm/mm-everything] [also build test ERROR on next-20220519] [cannot apply to linux/master linus/master v5.18-rc7] [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] url: https://github.com/intel-lab-lkp/linux/commits/zhenwei-pi/recover-hardware-corrupted-page-by-virtio-balloon/20220520-151328 base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything config: arm-randconfig-r026-20220519 (https://download.01.org/0day-ci/archive/20220520/202205202330.u0vqwiwg-...@intel.com/config) compiler: arm-linux-gnueabi-gcc (GCC) 11.3.0 reproduce (this is a W=1 build): wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # https://github.com/intel-lab-lkp/linux/commit/a42127073dd4adb6354649c8235c5cde033d01f2 git remote add linux-review https://github.com/intel-lab-lkp/linux git fetch --no-tags linux-review zhenwei-pi/recover-hardware-corrupted-page-by-virtio-balloon/20220520-151328 git checkout a42127073dd4adb6354649c8235c5cde033d01f2 # save the config file mkdir build_dir && cp config build_dir/.config COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash If you fix the issue, kindly add following tag where applicable Reported-by: kernel test robot All errors (new ones prefixed by >>): arm-linux-gnueabi-ld: drivers/virtio/virtio_balloon.o: in function `unpoison_memory_func': >> virtio_balloon.c:(.text+0x89a): undefined reference to `unpoison_memory' arm-linux-gnueabi-ld: drivers/virtio/virtio_balloon.o: in function `virtballoon_probe': >> virtio_balloon.c:(.text+0x111a): undefined reference to >> `register_memory_failure_notifier' arm-linux-gnueabi-ld: drivers/virtio/virtio_balloon.o: in function `virtballoon_remove': >> virtio_balloon.c:(.text+0x12a2): undefined reference to >> `unregister_memory_failure_notifier' -- 0-DAY CI Kernel Test Service https://01.org/lkp
Re: [PATCH 3/3] virtio_balloon: Introduce memory recover
Hi zhenwei,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on akpm-mm/mm-everything]
[also build test ERROR on next-20220519]
[cannot apply to linux/master linus/master v5.18-rc7]
[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]
url:
https://github.com/intel-lab-lkp/linux/commits/zhenwei-pi/recover-hardware-corrupted-page-by-virtio-balloon/20220520-151328
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git
mm-everything
config: nios2-randconfig-r002-20220519
(https://download.01.org/0day-ci/archive/20220520/202205202151.7t3k7szf-...@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.3.0
reproduce (this is a W=1 build):
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin/make.cross
#
https://github.com/intel-lab-lkp/linux/commit/a42127073dd4adb6354649c8235c5cde033d01f2
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review
zhenwei-pi/recover-hardware-corrupted-page-by-virtio-balloon/20220520-151328
git checkout a42127073dd4adb6354649c8235c5cde033d01f2
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1
O=build_dir ARCH=nios2 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot
All errors (new ones prefixed by >>):
nios2-linux-ld: drivers/virtio/virtio_balloon.o: in function
`unpoison_memory_func':
>> drivers/virtio/virtio_balloon.c:679: undefined reference to `unpoison_memory'
drivers/virtio/virtio_balloon.c:679:(.text+0xc00): relocation truncated to
fit: R_NIOS2_CALL26 against `unpoison_memory'
nios2-linux-ld: drivers/virtio/virtio_balloon.o: in function
`virtballoon_probe':
>> drivers/virtio/virtio_balloon.c:1247: undefined reference to
>> `register_memory_failure_notifier'
drivers/virtio/virtio_balloon.c:1247:(.text+0x1940): relocation truncated to
fit: R_NIOS2_CALL26 against `register_memory_failure_notifier'
nios2-linux-ld: drivers/virtio/virtio_balloon.o: in function
`virtballoon_remove':
>> drivers/virtio/virtio_balloon.c:1323: undefined reference to
>> `unregister_memory_failure_notifier'
drivers/virtio/virtio_balloon.c:1323:(.text+0x1bcc): relocation truncated to
fit: R_NIOS2_CALL26 against `unregister_memory_failure_notifier'
vim +679 drivers/virtio/virtio_balloon.c
661
662 static void unpoison_memory_func(struct work_struct *work)
663 {
664 struct virtio_balloon *vb;
665 struct page *page;
666
667 vb = container_of(work, struct virtio_balloon,
unpoison_memory_work);
668
669 do {
670 spin_lock(>recover_page_list_lock);
671 page =
list_first_entry_or_null(>recovered_page_list,
672 struct page, lru);
673 if (page)
674 list_del(>lru);
675 spin_unlock(>recover_page_list_lock);
676
677 if (page) {
678 put_page(page);
> 679 unpoison_memory(page_to_pfn(page), true,
> "virtio-balloon");
680 }
681 } while (page);
682 }
683
--
0-DAY CI Kernel Test Service
https://01.org/lkp
Re: [PATCH 3/3] virtio_balloon: Introduce memory recover
Hi zhenwei,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on akpm-mm/mm-everything]
[also build test WARNING on next-20220519]
[cannot apply to linux/master linus/master v5.18-rc7]
[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]
url:
https://github.com/intel-lab-lkp/linux/commits/zhenwei-pi/recover-hardware-corrupted-page-by-virtio-balloon/20220520-151328
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git
mm-everything
config: hexagon-randconfig-r041-20220519
(https://download.01.org/0day-ci/archive/20220520/202205202014.mgqgbrkd-...@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project
e00cbbec06c08dc616a0d52a20f678b8fbd4e304)
reproduce (this is a W=1 build):
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin/make.cross
#
https://github.com/intel-lab-lkp/linux/commit/a42127073dd4adb6354649c8235c5cde033d01f2
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review
zhenwei-pi/recover-hardware-corrupted-page-by-virtio-balloon/20220520-151328
git checkout a42127073dd4adb6354649c8235c5cde033d01f2
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1
O=build_dir ARCH=hexagon SHELL=/bin/bash drivers/virtio/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot
All warnings (new ones prefixed by >>):
>> drivers/virtio/virtio_balloon.c:654:2: warning: unannotated fall-through
>> between switch labels [-Wimplicit-fallthrough]
default:
^
drivers/virtio/virtio_balloon.c:654:2: note: insert 'break;' to avoid
fall-through
default:
^
break;
1 warning generated.
vim +654 drivers/virtio/virtio_balloon.c
593
594 static void recover_vq_handle_response(struct virtio_balloon *vb,
unsigned int len)
595 {
596 struct __virtio_balloon_recover *in_vbr;
597 struct virtio_balloon_recover *vbr;
598 struct page *page;
599 unsigned int pfns;
600 u32 pfn0, pfn1;
601 __u8 status;
602
603 /* the response is not expected */
604 if (unlikely(len != sizeof(struct __virtio_balloon_recover)))
605 return;
606
607 in_vbr = >in_vbr;
608 vbr = _vbr->vbr;
609 if (unlikely(vbr->cmd != VIRTIO_BALLOON_R_CMD_RESPONSE))
610 return;
611
612 /* to make sure the contiguous balloon PFNs */
613 for (pfns = 1; pfns < VIRTIO_BALLOON_PAGES_PER_PAGE; pfns++) {
614 pfn0 = virtio32_to_cpu(vb->vdev, in_vbr->pfns[pfns -
1]);
615 pfn1 = virtio32_to_cpu(vb->vdev, in_vbr->pfns[pfns]);
616 if (pfn1 - pfn0 != 1)
617 return;
618 }
619
620 pfn0 = virtio32_to_cpu(vb->vdev, in_vbr->pfns[0]);
621 if (!pfn_valid(pfn0))
622 return;
623
624 pfn1 = -1;
625 spin_lock(>recover_page_list_lock);
626 list_for_each_entry(page, >corrupted_page_list, lru) {
627 pfn1 = page_to_pfn(page);
628 if (pfn1 == pfn0)
629 break;
630 }
631 spin_unlock(>recover_page_list_lock);
632
633 status = vbr->status;
634 switch (status) {
635 case VIRTIO_BALLOON_R_STATUS_RECOVERED:
636 if (pfn1 == pfn0) {
637 spin_lock(>recover_page_list_lock);
638 list_del(>lru);
639 balloon_page_push(>recovered_page_list,
page);
640 spin_unlock(>recover_page_list_lock);
641 queue_work(system_freezable_wq,
>unpoison_memory_work);
642 dev_info_ratelimited(>vdev->dev, "recovered
pfn 0x%x", pfn0);
643 }
644 break;
645 case VIRTIO_BALLOON_R_STATUS_FAILED:
646 /* the hypervisor can't fix this corrupted page,
balloon puts page */
647 if (pfn1 == pfn0) {
648 spin_lock(>recover_page_list_lock);
649 list_del(>lru);
650 spin_unlock(>recover_page_list_lock);
651 put_page(page);
652
Re: [PATCH 2/5 v4] KVM: SVM: Fill in conforming svm_x86_ops via macro
Hi Krish,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.10-rc3 next-20201109]
[cannot apply to vhost/linux-next kvmarm/next kvm/linux-next kvms390/next]
[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]
url:
https://github.com/0day-ci/linux/commits/Krish-Sadhukhan/KVM-x86-Fill-in-conforming-vmx-svm-_x86_ops-and-vmx-svm-_nested_ops-via-macros/20201110-095653
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
407ab579637ced6dc32cfb2295afb7259cca4b22
config: i386-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
#
https://github.com/0day-ci/linux/commit/26275e3a7e11da29dc47a214b3938e7261c61ec7
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review
Krish-Sadhukhan/KVM-x86-Fill-in-conforming-vmx-svm-_x86_ops-and-vmx-svm-_nested_ops-via-macros/20201110-095653
git checkout 26275e3a7e11da29dc47a214b3938e7261c61ec7
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot
All warnings (new ones prefixed by >>):
>> arch/x86/kvm/svm/svm.c:1651:6: warning: no previous prototype for
>> 'svm_get_cs_db_l_bits' [-Wmissing-prototypes]
1651 | void svm_get_cs_db_l_bits(struct kvm_vcpu *vcpu, int *db, int *l)
| ^~~~
>> arch/x86/kvm/svm/svm.c:3372:6: warning: no previous prototype for
>> 'svm_tlb_flush_all' [-Wmissing-prototypes]
3372 | void svm_tlb_flush_all(struct kvm_vcpu *vcpu)
| ^
>> arch/x86/kvm/svm/svm.c:3377:6: warning: no previous prototype for
>> 'svm_tlb_flush_current' [-Wmissing-prototypes]
3377 | void svm_tlb_flush_current(struct kvm_vcpu *vcpu)
| ^
>> arch/x86/kvm/svm/svm.c:3382:6: warning: no previous prototype for
>> 'svm_tlb_flush_guest' [-Wmissing-prototypes]
3382 | void svm_tlb_flush_guest(struct kvm_vcpu *vcpu)
| ^~~
vim +/svm_get_cs_db_l_bits +1651 arch/x86/kvm/svm/svm.c
1650
> 1651 void svm_get_cs_db_l_bits(struct kvm_vcpu *vcpu, int *db, int *l)
1652 {
1653 struct kvm_segment cs;
1654
1655 kvm_get_segment(vcpu, , VCPU_SREG_CS);
1656 *db = cs.db;
1657 *l = cs.l;
1658 }
1659
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-...@lists.01.org
.config.gz
Description: application/gzip
[Qemu-devel] [lkp-robot] [fw_cfg] 9f0f3ea314: BUG:KASAN:null-ptr-deref_on_address
FYI, we noticed the following commit:
commit: 9f0f3ea31419e56d861441b2d863e992d13f19d7 ("fw_cfg: do DMA read
operation")
url:
https://github.com/0day-ci/linux/commits/marcandre-lureau-redhat-com/fw_cfg-add-DMA-operations/20170429-202925
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm -cpu host -smp 2 -m 4G
caused below changes (please refer to attached dmesg/kmsg for entire
log/backtrace):
+--+++
| | c0bbc7cf8b
| 9f0f3ea314 |
+--+++
| boot_successes | 6
| 0 |
| boot_failures| 2
| 8 |
| invoked_oom-killer:gfp_mask=0x | 2
| 2 |
| Mem-Info | 2
| 2 |
| Kernel_panic-not_syncing:Out_of_memory_and_no_killable_processes | 2
| 2 |
| BUG:kernel_hang_in_test_stage| 0
| 2 |
| BUG:KASAN:null-ptr-deref_on_address | 0
| 4 |
| BUG:unable_to_handle_kernel | 0
| 4 |
| Oops:#[##] | 0
| 4 |
| Kernel_panic-not_syncing:Fatal_exception | 0
| 4 |
+--+++
[ 276.979741] BUG: KASAN: null-ptr-deref on address 0390
[ 276.979741] BUG: KASAN: null-ptr-deref on address 0390
[ 276.979778] Read of size 8 by task swapper/1
[ 276.979778] Read of size 8 by task swapper/1
[ 276.979841] CPU: 0 PID: 1 Comm: swapper Not tainted
4.11.0-rc8-00089-g9f0f3ea #2
[ 276.979841] CPU: 0 PID: 1 Comm: swapper Not tainted
4.11.0-rc8-00089-g9f0f3ea #2
[ 276.979878] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
1.9.3-20161025_171302-gandalf 04/01/2014
[ 276.979878] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
1.9.3-20161025_171302-gandalf 04/01/2014
[ 276.979910] Call Trace:
[ 276.979910] Call Trace:
[ 276.980004] dump_stack+0x19/0x1b
[ 276.980004] dump_stack+0x19/0x1b
[ 276.980131] kasan_report+0x467/0x560
[ 276.980131] kasan_report+0x467/0x560
[ 276.980197] ? swiotlb_map_page+0x54/0x248
[ 276.980197] ? swiotlb_map_page+0x54/0x248
[ 276.980260] ? kasan_unpoison_shadow+0x35/0x43
[ 276.980260] ? kasan_unpoison_shadow+0x35/0x43
[ 276.980324] ? swiotlb_free_coherent+0x9a/0x9a
[ 276.980324] ? swiotlb_free_coherent+0x9a/0x9a
[ 276.980387] __asan_load8+0x5e/0x6f
[ 276.980387] __asan_load8+0x5e/0x6f
[ 276.980428] swiotlb_map_page+0x54/0x248
[ 276.980428] swiotlb_map_page+0x54/0x248
[ 276.980493] ? swiotlb_free_coherent+0x9a/0x9a
[ 276.980493] ? swiotlb_free_coherent+0x9a/0x9a
[ 276.980581] fw_cfg_dma_transfer+0xb9/0x39c
[ 276.980581] fw_cfg_dma_transfer+0xb9/0x39c
[ 276.980649] fw_cfg_read_blob+0xf0/0x201
[ 276.980649] fw_cfg_read_blob+0xf0/0x201
[ 276.980715] ? fw_cfg_dma_transfer+0x39c/0x39c
[ 276.980715] ? fw_cfg_dma_transfer+0x39c/0x39c
[ 276.980782] ? __kmalloc+0x15f/0x304
[ 276.980782] ? __kmalloc+0x15f/0x304
[ 276.980844] ? fw_cfg_sysfs_probe+0x2c9/0x84a
[ 276.980844] ? fw_cfg_sysfs_probe+0x2c9/0x84a
[ 276.980911] fw_cfg_sysfs_probe+0x2f4/0x84a
[ 276.980911] fw_cfg_sysfs_probe+0x2f4/0x84a
[ 276.980980] ? fw_cfg_sysfs_read_raw+0x70/0x70
[ 276.980980] ? fw_cfg_sysfs_read_raw+0x70/0x70
[ 276.981104] ? acpi_device_wakeup+0x3d/0x110
[ 276.981104] ? acpi_device_wakeup+0x3d/0x110
[ 276.981172] ? acpi_dev_pm_attach+0xf0/0x12e
[ 276.981172] ? acpi_dev_pm_attach+0xf0/0x12e
[ 276.981239] platform_drv_probe+0x54/0xd2
[ 276.981239] platform_drv_probe+0x54/0xd2
[ 276.981330] driver_probe_device+0x2b1/0x730
[ 276.981330] driver_probe_device+0x2b1/0x730
[ 276.981401] ? driver_probe_device+0x730/0x730
[ 276.981401] ? driver_probe_device+0x730/0x730
[ 276.981488] __driver_attach+0x121/0x123
[ 276.981488] __driver_attach+0x121/0x123
[ 276.981556] bus_for_each_dev+0xeb/0x147
[ 276.981556] bus_for_each_dev+0xeb/0x147
[ 276.981623] ? store_drivers_autoprobe+0x80/0x80
[ 276.981623] ? store_drivers_autoprobe+0x80/0x80
[ 276.981688] ? _raw_spin_unlock+0x27/0x3a
[ 276.981688] ? _raw_spin_unlock+0x27/0x3a
[ 276.981756] driver_attach+0x2b/0x2e
[ 276.981756] driver_attach+0x2b/0x2e
[ 276.981823] bus_add_driver+0x27e/0x39c
[ 276.981823] bus_add_driver+0x27e/0x39c
[ 276.981887] driver_register+0xd3/0x193
[ 276.981887] driver_register+0xd3/0x193
[ 276.981975] ? firmware_map_add_early+0x5b/0x5b
[ 276.981975] ?
