Re: [PATCH v2 2/6] trace: add CONFIG_BUILTIN_MODULE_RANGES option
Hi Kris, kernel test robot noticed the following build warnings: [auto build test WARNING on dd5a440a31fae6e459c0d627162825505361] url: https://github.com/intel-lab-lkp/linux/commits/Kris-Van-Hees/kbuild-add-modules-builtin-objs/20240512-065954 base: dd5a440a31fae6e459c0d627162825505361 patch link: https://lore.kernel.org/r/20240511224035.27775-3-kris.van.hees%40oracle.com patch subject: [PATCH v2 2/6] trace: add CONFIG_BUILTIN_MODULE_RANGES option config: arc-kismet-CONFIG_VMLINUX_MAP-CONFIG_BUILTIN_MODULE_RANGES-0-0 (https://download.01.org/0day-ci/archive/20240515/202405150623.lms5svhm-...@intel.com/config) reproduce: (https://download.01.org/0day-ci/archive/20240515/202405150623.lms5svhm-...@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/202405150623.lms5svhm-...@intel.com/ kismet warnings: (new ones prefixed by >>) >> kismet: WARNING: unmet direct dependencies detected for VMLINUX_MAP when >> selected by BUILTIN_MODULE_RANGES WARNING: unmet direct dependencies detected for VMLINUX_MAP Depends on [n]: EXPERT [=n] Selected by [y]: - BUILTIN_MODULE_RANGES [=y] && FTRACE [=y] -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH 2/2] drivers: remoteproc: xlnx: add sram support
Hi Tanmay,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 0496190c4d42965acb31b9da1b6dac3509791062]
url:
https://github.com/intel-lab-lkp/linux/commits/Tanmay-Shah/drivers-remoteproc-xlnx-add-attach-detach-support/20240503-071225
base: 0496190c4d42965acb31b9da1b6dac3509791062
patch link:
https://lore.kernel.org/r/20240502231021.370047-3-tanmay.shah%40amd.com
patch subject: [PATCH 2/2] drivers: remoteproc: xlnx: add sram support
config: arm64-randconfig-r113-20240506
(https://download.01.org/0day-ci/archive/20240506/202405060759.yyzluqxp-...@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce:
(https://download.01.org/0day-ci/archive/20240506/202405060759.yyzluqxp-...@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/202405060759.yyzluqxp-...@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/remoteproc/xlnx_r5_remoteproc.c:423:20: sparse: sparse: cast removes
address space '__iomem' of expression
drivers/remoteproc/xlnx_r5_remoteproc.c:604:20: sparse: sparse: cast removes
address space '__iomem' of expression
drivers/remoteproc/xlnx_r5_remoteproc.c:827:21: sparse: sparse: incorrect
type in assignment (different address spaces) @@ expected struct
rsc_tbl_data *rsc_data_va @@ got void [noderef] __iomem * @@
drivers/remoteproc/xlnx_r5_remoteproc.c:827:21: sparse: expected struct
rsc_tbl_data *rsc_data_va
drivers/remoteproc/xlnx_r5_remoteproc.c:827:21: sparse: got void
[noderef] __iomem *
drivers/remoteproc/xlnx_r5_remoteproc.c:844:18: sparse: sparse: incorrect
type in assignment (different address spaces) @@ expected struct
resource_table *rsc_addr @@ got void [noderef] __iomem * @@
drivers/remoteproc/xlnx_r5_remoteproc.c:844:18: sparse: expected struct
resource_table *rsc_addr
drivers/remoteproc/xlnx_r5_remoteproc.c:844:18: sparse: got void
[noderef] __iomem *
drivers/remoteproc/xlnx_r5_remoteproc.c:898:24: sparse: sparse: incorrect
type in argument 1 (different address spaces) @@ expected void volatile
[noderef] __iomem *addr @@ got struct resource_table *rsc_tbl_va @@
drivers/remoteproc/xlnx_r5_remoteproc.c:898:24: sparse: expected void
volatile [noderef] __iomem *addr
drivers/remoteproc/xlnx_r5_remoteproc.c:898:24: sparse: got struct
resource_table *rsc_tbl_va
>> drivers/remoteproc/xlnx_r5_remoteproc.c:995:26: sparse: sparse: Using plain
>> integer as NULL pointer
vim +995 drivers/remoteproc/xlnx_r5_remoteproc.c
798
799 static int zynqmp_r5_get_rsc_table_va(struct zynqmp_r5_core *r5_core)
800 {
801 struct device *dev = r5_core->dev;
802 struct rsc_tbl_data *rsc_data_va;
803 struct resource_table *rsc_addr;
804 struct resource res_mem;
805 struct device_node *np;
806 int ret;
807
808 /**
809 * It is expected from remote processor firmware to provide
resource
810 * table address via struct rsc_tbl_data data structure.
811 * Start address of first entry under "memory-region" property
list
812 * contains that data structure which holds resource table
address, size
813 * and some magic number to validate correct resource table
entry.
814 */
815 np = of_parse_phandle(r5_core->np, "memory-region", 0);
816 if (!np) {
817 dev_err(dev, "failed to get memory region dev node\n");
818 return -EINVAL;
819 }
820
821 ret = of_address_to_resource(np, 0, _mem);
822 if (ret) {
823 dev_err(dev, "failed to get memory-region resource
addr\n");
824 return -EINVAL;
825 }
826
> 827 rsc_data_va = devm_ioremap_wc(dev, res_mem.start,
828sizeof(struct rsc_tbl_data));
829 if (!rsc_data_va) {
830 dev_err(dev, "failed to map resource table data
address\n");
831 return -EIO;
832 }
833
834 /**
835 * If RSC_TBL_XLNX_MAGIC number and its complement isn't found
then
836 * do not consider resource table address valid and don't attach
837 */
838 if (rsc_data_va->magic_num != RSC_TBL_XLNX_MAGIC ||
839 rsc_data_va->comp_magic_num != ~RSC_TBL_XLNX_MAGIC) {
840 dev_dbg(dev, "invalid magic number, won't attach\n");
841 return -EINVAL;
842 }
843
844 rsc_addr = ioremap_wc(r
Re: [PATCH 1/2] drivers: remoteproc: xlnx: add attach detach support
Hi Tanmay,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 0496190c4d42965acb31b9da1b6dac3509791062]
url:
https://github.com/intel-lab-lkp/linux/commits/Tanmay-Shah/drivers-remoteproc-xlnx-add-attach-detach-support/20240503-071225
base: 0496190c4d42965acb31b9da1b6dac3509791062
patch link:
https://lore.kernel.org/r/20240502231021.370047-2-tanmay.shah%40amd.com
patch subject: [PATCH 1/2] drivers: remoteproc: xlnx: add attach detach support
config: arm64-randconfig-r113-20240506
(https://download.01.org/0day-ci/archive/20240506/202405060611.jbqbf7ib-...@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce:
(https://download.01.org/0day-ci/archive/20240506/202405060611.jbqbf7ib-...@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/202405060611.jbqbf7ib-...@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/remoteproc/xlnx_r5_remoteproc.c:404:20: sparse: sparse: cast removes
address space '__iomem' of expression
drivers/remoteproc/xlnx_r5_remoteproc.c:522:20: sparse: sparse: cast removes
address space '__iomem' of expression
>> drivers/remoteproc/xlnx_r5_remoteproc.c:731:21: sparse: sparse: incorrect
>> type in assignment (different address spaces) @@ expected struct
>> rsc_tbl_data *rsc_data_va @@ got void [noderef] __iomem * @@
drivers/remoteproc/xlnx_r5_remoteproc.c:731:21: sparse: expected struct
rsc_tbl_data *rsc_data_va
drivers/remoteproc/xlnx_r5_remoteproc.c:731:21: sparse: got void
[noderef] __iomem *
>> drivers/remoteproc/xlnx_r5_remoteproc.c:748:18: sparse: sparse: incorrect
>> type in assignment (different address spaces) @@ expected struct
>> resource_table *rsc_addr @@ got void [noderef] __iomem * @@
drivers/remoteproc/xlnx_r5_remoteproc.c:748:18: sparse: expected struct
resource_table *rsc_addr
drivers/remoteproc/xlnx_r5_remoteproc.c:748:18: sparse: got void
[noderef] __iomem *
>> drivers/remoteproc/xlnx_r5_remoteproc.c:802:24: sparse: sparse: incorrect
>> type in argument 1 (different address spaces) @@ expected void volatile
>> [noderef] __iomem *addr @@ got struct resource_table *rsc_tbl_va @@
drivers/remoteproc/xlnx_r5_remoteproc.c:802:24: sparse: expected void
volatile [noderef] __iomem *addr
drivers/remoteproc/xlnx_r5_remoteproc.c:802:24: sparse: got struct
resource_table *rsc_tbl_va
vim +731 drivers/remoteproc/xlnx_r5_remoteproc.c
702
703 static int zynqmp_r5_get_rsc_table_va(struct zynqmp_r5_core *r5_core)
704 {
705 struct device *dev = r5_core->dev;
706 struct rsc_tbl_data *rsc_data_va;
707 struct resource_table *rsc_addr;
708 struct resource res_mem;
709 struct device_node *np;
710 int ret;
711
712 /**
713 * It is expected from remote processor firmware to provide
resource
714 * table address via struct rsc_tbl_data data structure.
715 * Start address of first entry under "memory-region" property
list
716 * contains that data structure which holds resource table
address, size
717 * and some magic number to validate correct resource table
entry.
718 */
719 np = of_parse_phandle(r5_core->np, "memory-region", 0);
720 if (!np) {
721 dev_err(dev, "failed to get memory region dev node\n");
722 return -EINVAL;
723 }
724
725 ret = of_address_to_resource(np, 0, _mem);
726 if (ret) {
727 dev_err(dev, "failed to get memory-region resource
addr\n");
728 return -EINVAL;
729 }
730
> 731 rsc_data_va = devm_ioremap_wc(dev, res_mem.start,
732sizeof(struct rsc_tbl_data));
733 if (!rsc_data_va) {
734 dev_err(dev, "failed to map resource table data
address\n");
735 return -EIO;
736 }
737
738 /**
739 * If RSC_TBL_XLNX_MAGIC number and its complement isn't found
then
740 * do not consider resource table address valid and don't attach
741 */
742 if (rsc_data_va->magic_num != RSC_TBL_XLNX_MAGIC ||
743 rsc_data_va->comp_magic_num != ~RSC_TBL_XLNX_MAGIC) {
744 dev_dbg(dev, "invalid magic number, won't attach\n");
745 return -EINVAL;
746 }
747
> 748 rsc_addr = ioremap_wc(rsc_data_va->rsc_tbl,
749
Re: [PATCH v8 3/6] LoongArch: KVM: Add cpucfg area for kvm hypervisor
Hi Bibo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 5eb4573ea63d0c83bf58fb7c243fc2c2b6966c02]
url:
https://github.com/intel-lab-lkp/linux/commits/Bibo-Mao/LoongArch-smp-Refine-some-ipi-functions-on-LoongArch-platform/20240428-180850
base: 5eb4573ea63d0c83bf58fb7c243fc2c2b6966c02
patch link:
https://lore.kernel.org/r/20240428100518.1642324-4-maobibo%40loongson.cn
patch subject: [PATCH v8 3/6] LoongArch: KVM: Add cpucfg area for kvm hypervisor
config: loongarch-defconfig
(https://download.01.org/0day-ci/archive/20240429/202404290016.t9p5ghvr-...@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240429/202404290016.t9p5ghvr-...@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/202404290016.t9p5ghvr-...@intel.com/
All warnings (new ones prefixed by >>):
arch/loongarch/kvm/exit.c: In function 'kvm_emu_cpucfg':
>> arch/loongarch/kvm/exit.c:213:23: warning: variable 'plv' set but not used
>> [-Wunused-but-set-variable]
213 | unsigned long plv;
| ^~~
vim +/plv +213 arch/loongarch/kvm/exit.c
208
209 static int kvm_emu_cpucfg(struct kvm_vcpu *vcpu, larch_inst inst)
210 {
211 int rd, rj;
212 unsigned int index;
> 213 unsigned long plv;
214
215 rd = inst.reg2_format.rd;
216 rj = inst.reg2_format.rj;
217 ++vcpu->stat.cpucfg_exits;
218 index = vcpu->arch.gprs[rj];
219
220 /*
221 * By LoongArch Reference Manual 2.2.10.5
222 * Return value is 0 for undefined cpucfg index
223 *
224 * Disable preemption since hw gcsr is accessed
225 */
226 preempt_disable();
227 plv = kvm_read_hw_gcsr(LOONGARCH_CSR_CRMD) >>
CSR_CRMD_PLV_SHIFT;
228 switch (index) {
229 case 0 ... (KVM_MAX_CPUCFG_REGS - 1):
230 vcpu->arch.gprs[rd] = vcpu->arch.cpucfg[index];
231 break;
232 case CPUCFG_KVM_SIG:
233 /* Cpucfg emulation between 0x4000 -- 0x40ff */
234 vcpu->arch.gprs[rd] = *(unsigned int *)KVM_SIGNATURE;
235 break;
236 default:
237 vcpu->arch.gprs[rd] = 0;
238 break;
239 }
240
241 preempt_enable();
242 return EMULATE_DONE;
243 }
244
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 3/4] vhost: Improve vhost_get_avail_head()
Hi Gavin,
kernel test robot noticed the following build warnings:
[auto build test WARNING on mst-vhost/linux-next]
[also build test WARNING on linus/master v6.9-rc5 next-20240424]
[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/Gavin-Shan/vhost-Drop-variable-last_avail_idx-in-vhost_get_vq_desc/20240423-112803
base: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
patch link:
https://lore.kernel.org/r/20240423032407.262329-4-gshan%40redhat.com
patch subject: [PATCH 3/4] vhost: Improve vhost_get_avail_head()
config: i386-randconfig-141-20240426
(https://download.01.org/0day-ci/archive/20240426/202404260448.g7f06v7m-...@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project
6009708b4367171ccdbf4b5905cb6a803753fe18)
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/202404260448.g7f06v7m-...@intel.com/
smatch warnings:
drivers/vhost/vhost.c:2614 vhost_get_vq_desc() warn: unsigned 'head' is never
less than zero.
drivers/vhost/vhost.c:2614 vhost_get_vq_desc() warn: error code type promoted
to positive: 'head'
vim +/head +2614 drivers/vhost/vhost.c
2581
2582 /* This looks in the virtqueue and for the first available buffer, and
converts
2583 * it to an iovec for convenient access. Since descriptors consist of
some
2584 * number of output then some number of input descriptors, it's
actually two
2585 * iovecs, but we pack them into one and note how many of each there
were.
2586 *
2587 * This function returns the descriptor number found, or vq->num (which
is
2588 * never a valid descriptor number) if none was found. A negative code
is
2589 * returned on error. */
2590 int vhost_get_vq_desc(struct vhost_virtqueue *vq,
2591struct iovec iov[], unsigned int iov_size,
2592unsigned int *out_num, unsigned int *in_num,
2593struct vhost_log *log, unsigned int *log_num)
2594 {
2595 struct vring_desc desc;
2596 unsigned int i, head, found = 0;
2597 int ret, access;
2598
2599 if (vq->avail_idx == vq->last_avail_idx) {
2600 ret = vhost_get_avail_idx(vq);
2601 if (unlikely(ret))
2602 return ret;
2603
2604 /* If there's nothing new since last we looked, return
2605 * invalid.
2606 */
2607 if (vq->avail_idx == vq->last_avail_idx)
2608 return vq->num;
2609 }
2610
2611 /* Grab the next descriptor number they're advertising, and
increment
2612 * the index we've seen. */
2613 head = vhost_get_avail_head(vq);
> 2614 if (unlikely(head < 0))
2615 return head;
2616
2617 /* When we start there are none of either input nor output. */
2618 *out_num = *in_num = 0;
2619 if (unlikely(log))
2620 *log_num = 0;
2621
2622 i = head;
2623 do {
2624 unsigned iov_count = *in_num + *out_num;
2625 if (unlikely(i >= vq->num)) {
2626 vq_err(vq, "Desc index is %u > %u, head = %u",
2627 i, vq->num, head);
2628 return -EINVAL;
2629 }
2630 if (unlikely(++found > vq->num)) {
2631 vq_err(vq, "Loop detected: last one at %u "
2632 "vq size %u head %u\n",
2633 i, vq->num, head);
2634 return -EINVAL;
2635 }
2636 ret = vhost_get_desc(vq, , i);
2637 if (unlikely(ret)) {
2638 vq_err(vq, "Failed to get descriptor: idx %d
addr %p\n",
2639 i, vq->desc + i);
2640 return -EFAULT;
2641 }
2642 if (desc.flags & cpu_to_vhost16(vq,
VRING_DESC_F_INDIRECT)) {
2643 ret = get_indirect(vq, iov, iov_size,
2644 out_num, in_num,
2645 log, log_num, );
2646 if (unlikely(ret < 0)) {
2647 if (ret !=
Re: [PATCH v2 2/6] iio: light: stk3310: Implement vdd supply and power it off during suspend
Hi Aren,
kernel test robot noticed the following build warnings:
[auto build test WARNING on jic23-iio/togreg]
[also build test WARNING on sunxi/sunxi/for-next robh/for-next linus/master
v6.9-rc5 next-20240423]
[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/Aren-Moynihan/dt-bindings-iio-light-stk33xx-add-vdd-and-leda-regulators/20240424-064250
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
patch link:
https://lore.kernel.org/r/20240423223309.1468198-4-aren%40peacevolution.org
patch subject: [PATCH v2 2/6] iio: light: stk3310: Implement vdd supply and
power it off during suspend
config: arm64-randconfig-001-20240424
(https://download.01.org/0day-ci/archive/20240424/202404242057.pudy5rb1-...@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project
5ef5eb66fb428aaf61fb51b709f065c069c11242)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240424/202404242057.pudy5rb1-...@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/202404242057.pudy5rb1-...@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/iio/light/stk3310.c:10:
In file included from include/linux/i2c.h:19:
In file included from include/linux/regulator/consumer.h:35:
In file included from include/linux/suspend.h:5:
In file included from include/linux/swap.h:9:
In file included from include/linux/memcontrol.h:21:
In file included from include/linux/mm.h:2208:
include/linux/vmstat.h:522:36: warning: arithmetic between different
enumeration types ('enum node_stat_item' and 'enum lru_list')
[-Wenum-enum-conversion]
522 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~ ^ ~~~
>> drivers/iio/light/stk3310.c:615:38: warning: variable 'ret' is uninitialized
>> when used here [-Wuninitialized]
615 | return dev_err_probe(>dev, ret, "get
regulator vdd failed\n");
|^~~
drivers/iio/light/stk3310.c:594:9: note: initialize the variable 'ret' to
silence this warning
594 | int ret;
|^
| = 0
2 warnings generated.
vim +/ret +615 drivers/iio/light/stk3310.c
591
592 static int stk3310_probe(struct i2c_client *client)
593 {
594 int ret;
595 struct iio_dev *indio_dev;
596 struct stk3310_data *data;
597
598 indio_dev = devm_iio_device_alloc(>dev, sizeof(*data));
599 if (!indio_dev) {
600 dev_err(>dev, "iio allocation failed!\n");
601 return -ENOMEM;
602 }
603
604 data = iio_priv(indio_dev);
605 data->client = client;
606 i2c_set_clientdata(client, indio_dev);
607
608 device_property_read_u32(>dev, "proximity-near-level",
609 >ps_near_level);
610
611 mutex_init(>lock);
612
613 data->vdd_reg = devm_regulator_get(>dev, "vdd");
614 if (IS_ERR(data->vdd_reg))
> 615 return dev_err_probe(>dev, ret, "get regulator
> vdd failed\n");
616
617 ret = stk3310_regmap_init(data);
618 if (ret < 0)
619 return ret;
620
621 indio_dev->info = _info;
622 indio_dev->name = STK3310_DRIVER_NAME;
623 indio_dev->modes = INDIO_DIRECT_MODE;
624 indio_dev->channels = stk3310_channels;
625 indio_dev->num_channels = ARRAY_SIZE(stk3310_channels);
626
627 ret = regulator_enable(data->vdd_reg);
628 if (ret)
629 return dev_err_probe(>dev, ret,
630 "regulator vdd enable failed\n");
631
632 /* we need a short delay to allow the chip time to power on */
633 fsleep(1000);
634
635 ret = stk3310_init(indio_dev);
636 if (ret < 0)
637 goto err_vdd_disable;
638
639 if (client->irq > 0) {
640 ret = devm_request_threaded_irq(>dev,
client->irq,
641 stk3310_irq_handler,
Re: [PATCH 2/3] virtio_balloon: introduce memory allocation stall counter
Hi zhenwei,
kernel test robot noticed the following build warnings:
[auto build test WARNING on akpm-mm/mm-everything]
[also build test WARNING 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/zhenwei-pi/virtio_balloon-introduce-oom-kill-invocations/20240418-142934
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git
mm-everything
patch link:
https://lore.kernel.org/r/20240418062602.1291391-3-pizhenwei%40bytedance.com
patch subject: [PATCH 2/3] virtio_balloon: introduce memory allocation stall
counter
config: i386-randconfig-141-20240421
(https://download.01.org/0day-ci/archive/20240421/202404211106.b9pwufqk-...@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project
6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240421/202404211106.b9pwufqk-...@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/202404211106.b9pwufqk-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/virtio/virtio_balloon.c:324:18: warning: unused variable 'stall'
>> [-Wunused-variable]
324 | long available, stall = 0;
| ^
1 warning generated.
vim +/stall +324 drivers/virtio/virtio_balloon.c
318
319 static unsigned int update_balloon_stats(struct virtio_balloon *vb)
320 {
321 unsigned long events[NR_VM_EVENT_ITEMS];
322 struct sysinfo i;
323 unsigned int idx = 0;
> 324 long available, stall = 0;
325 unsigned long caches;
326
327 all_vm_events(events);
328 si_meminfo();
329
330 available = si_mem_available();
331 caches = global_node_page_state(NR_FILE_PAGES);
332
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[linus:master] [trace_seq] 40fc60e36c: BUG:KASAN:global-out-of-bounds_in_hex_string
Hello,
kernel test robot noticed "BUG:KASAN:global-out-of-bounds_in_hex_string" on:
commit: 40fc60e36c60ba85b2974e507b67df40c94e9578 ("trace_seq: Increase the
buffer size to almost two pages")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 6c6e47d69d821047097909288b6d7f1aafb3b9b1]
[test failed on linux-next/master 8568bb2ccc278f344e6ac44af6ed010a90aa88dc]
in testcase: rcuscale
version:
with following parameters:
runtime: 300s
scale_type: tasks
compiler: clang-17
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
we also noticed this issue does not always happen. we observed it 17 times
out of 30 runs as below, but did not observe it on parent.
8ec90be7f15fac42 40fc60e36c60ba85b2974e507b6
---
fail:runs %reproductionfail:runs
| | |
:30 57% 17:30
dmesg.BUG:KASAN:global-out-of-bounds_in_hex_string
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-lkp/202404101431.bb9742bf-...@intel.com
[ 413.751080][ T494] BUG: KASAN: global-out-of-bounds in hex_string
(lib/vsprintf.c:?)
[ 413.752115][ T494] Read of size 1 at addr 960c19c4 by task
rcu_scale_write/494
[ 413.753237][ T494]
[ 413.753659][ T494] CPU: 0 PID: 494 Comm: rcu_scale_write Tainted: G
T 6.7.0-rc2-00035-g40fc60e36c60 #1
a4d5f5b4375fec29a5dddc8a474a6031f87af2c2
[ 413.755544][ T494] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 413.756859][ T494] Call Trace:
[ 413.757375][ T494]
[ 413.757850][ T494] dump_stack_lvl (lib/dump_stack.c:?)
[ 413.758486][ T494] print_report (mm/kasan/report.c:365)
[ 413.759147][ T494] ? hex_string (lib/vsprintf.c:?)
[ 413.759803][ T494] kasan_report (mm/kasan/report.c:590)
[ 413.760455][ T494] ? hex_string (lib/vsprintf.c:?)
[ 413.761099][ T494] hex_string (lib/vsprintf.c:?)
[ 413.761719][ T494] pointer (lib/vsprintf.c:?)
[ 413.762328][ T494] vsnprintf (lib/vsprintf.c:2823)
[ 413.762978][ T494] seq_buf_vprintf (lib/seq_buf.c:64)
[ 413.763647][ T494] trace_seq_vprintf (include/linux/seq_buf.h:53
kernel/trace/trace_seq.c:151)
[ 413.764351][ T494] trace_event_printf (kernel/trace/trace_output.c:325)
[ 413.765043][ T494] trace_raw_output_i2c_write (include/trace/events/i2c.h:25)
i2c_core
[ 413.766410][ T494] ? i2c_put_dma_safe_msg_buf (include/trace/events/i2c.h:25)
i2c_core
[ 413.767794][ T494] ftrace_dump (kernel/trace/trace.c:10262)
[ 413.768472][ T494] rcu_scale_writer (kernel/rcu/rcuscale.c:535) rcuscale
[ 413.769741][ T494] ? rcu_scale_writer (kernel/rcu/rcuscale.c:526) rcuscale
[ 413.771241][ T494] kthread (kernel/kthread.c:390)
[ 413.771847][ T494] ? rcu_scale_reader (kernel/rcu/rcuscale.c:453) rcuscale
[ 413.773073][ T494] ? kthread_unuse_mm (kernel/kthread.c:341)
[ 413.773791][ T494] ret_from_fork (arch/x86/kernel/process.c:153)
[ 413.774441][ T494] ? kthread_unuse_mm (kernel/kthread.c:341)
[ 413.775186][ T494] ret_from_fork_asm (arch/x86/entry/entry_64.S:250)
[ 413.775893][ T494]
[ 413.776406][ T494]
[ 413.776859][ T494] The buggy address belongs to the variable:
[ 413.777635][ T494] btf_allowlist_d_path+0x4/0x20
[ 413.778325][ T494]
[ 413.778740][ T494] The buggy address belongs to the physical page:
[ 413.779592][ T494] page:ea00074c3040 refcount:1 mapcount:0
mapping: index:0x0 pfn:0x1d30c1
[ 413.780914][ T494] flags: 0x80004000(reserved|zone=2)
[ 413.781710][ T494] page_type: 0x()
[ 413.782341][ T494] raw: 80004000 ea00074c3048 ea00074c3048
[ 413.783501][ T494] raw: 0001
[ 413.784669][ T494] page dumped because: kasan: bad access detected
[ 413.785556][ T494] page_owner info is not present (never set?)
[ 413.786370][ T494]
[ 413.786789][ T494] Memory state around the buggy address:
[ 413.787550][ T494] 960c1880: 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
[ 413.788643][ T494] 960c1900: 00 00 00 00 f9 f9 f9 f9 f9 f9 f9 f9
00 f9 f9 f9
[ 413.789739][ T494] >960c1980: 04 f9 f9 f9 04 f9 f9 f9 04 f9 f9 f9
00 00 00 f9
[ 413.790848][ T494]^
[ 413.791705][ T494] 960c1a00: f9 f9 f9 f9 00 f9 f9 f9 00 f9 f9 f9
04 f9 f9 f9
[ 413.792789][ T494] 960c1a80: 01 f9 f9 f9 01 f9 f9 f9 00 00 f9 f9
00 00 f9 f9
[ 413.797442][ T494]
==
[ 413.798544][ T494] Disabling lock debugging due to kernel taint
[ 413.799401][ T494]
Re: [PATCH 2/3] kernel/pid: Remove default pid_max value
Hi Michal,
kernel test robot noticed the following build errors:
[auto build test ERROR on fec50db7033ea478773b159e0e2efb135270e3b7]
url:
https://github.com/intel-lab-lkp/linux/commits/Michal-Koutn/tracing-Remove-dependency-of-saved_cmdlines_buffer-on-PID_MAX_DEFAULT/20240408-230031
base: fec50db7033ea478773b159e0e2efb135270e3b7
patch link:
https://lore.kernel.org/r/20240408145819.8787-3-mkoutny%40suse.com
patch subject: [PATCH 2/3] kernel/pid: Remove default pid_max value
config: arm-allnoconfig
(https://download.01.org/0day-ci/archive/20240409/202404090903.3jz667sn-...@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project
8b3b4a92adee40483c27f26c478a384cd69c6f05)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240409/202404090903.3jz667sn-...@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/202404090903.3jz667sn-...@intel.com/
All errors (new ones prefixed by >>):
In file included from kernel/sysctl.c:23:
In file included from include/linux/mm.h:2208:
include/linux/vmstat.h:522:36: warning: arithmetic between different
enumeration types ('enum node_stat_item' and 'enum lru_list')
[-Wenum-enum-conversion]
522 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~ ^ ~~~
>> kernel/sysctl.c:1819:14: error: initializing 'void *' with an expression of
>> type 'const int *' discards qualifiers
>> [-Werror,-Wincompatible-pointer-types-discards-qualifiers]
1819 | .extra2 = _max_max,
| ^~~~
1 warning and 1 error generated.
vim +1819 kernel/sysctl.c
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1617
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1618 static struct ctl_table
kern_table[] = {
^1da177e4c3f41 Linus Torvalds 2005-04-16 1619 {
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1620 .procname
= "panic",
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1621 .data
= _timeout,
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1622 .maxlen
= sizeof(int),
49f0ce5f92321c Jerome Marchand 2014-01-21 1623 .mode
= 0644,
6d4561110a3e9f Eric W. Biederman 2009-11-16 1624 .proc_handler
= proc_dointvec,
^1da177e4c3f41 Linus Torvalds 2005-04-16 1625 },
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1626 #ifdef CONFIG_PROC_SYSCTL
^1da177e4c3f41 Linus Torvalds 2005-04-16 1627 {
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1628 .procname
= "tainted",
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1629 .maxlen
= sizeof(long),
^1da177e4c3f41 Linus Torvalds 2005-04-16 1630 .mode
= 0644,
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1631 .proc_handler
= proc_taint,
^1da177e4c3f41 Linus Torvalds 2005-04-16 1632 },
2da02997e08d3e David Rientjes 2009-01-06 1633 {
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1634 .procname
= "sysctl_writes_strict",
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1635 .data
= _writes_strict,
9e3961a0979817 Prarit Bhargava 2014-12-10 1636 .maxlen
= sizeof(int),
2da02997e08d3e David Rientjes 2009-01-06 1637 .mode
= 0644,
9e3961a0979817 Prarit Bhargava 2014-12-10 1638 .proc_handler
= proc_dointvec_minmax,
78e36f3b0dae58 Xiaoming Ni 2022-01-21 1639 .extra1
= SYSCTL_NEG_ONE,
eec4844fae7c03 Matteo Croce2019-07-18 1640 .extra2
= SYSCTL_ONE,
2da02997e08d3e David Rientjes 2009-01-06 1641 },
964c9dff009189 Alexander Popov 2018-08-17 1642 #endif
1efff914afac8a Theodore Ts'o 2015-03-17 1643 {
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1644 .procname
= "print-fatal-signals",
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1645 .data
= _fatal_signals,
964c9dff009189 Alexander Popov 2018-08-17 1646 .maxlen
= sizeof(int),
1efff914afac8a Theodore Ts'o 2015-03-17 1647 .mode
= 0644,
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1648 .proc_handler
= proc_dointvec,
1efff914afac8a Theodore Ts'o 2015-03-17 1649 },
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1650 #ifdef CONFIG_SPARC
^1da177e4c3f41 Linus Torvalds 2005-04-16 1651 {
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1652 .procname
= "reb
Re: [PATCH 2/3] kernel/pid: Remove default pid_max value
Hi Michal,
kernel test robot noticed the following build warnings:
[auto build test WARNING on fec50db7033ea478773b159e0e2efb135270e3b7]
url:
https://github.com/intel-lab-lkp/linux/commits/Michal-Koutn/tracing-Remove-dependency-of-saved_cmdlines_buffer-on-PID_MAX_DEFAULT/20240408-230031
base: fec50db7033ea478773b159e0e2efb135270e3b7
patch link:
https://lore.kernel.org/r/20240408145819.8787-3-mkoutny%40suse.com
patch subject: [PATCH 2/3] kernel/pid: Remove default pid_max value
config: alpha-allnoconfig
(https://download.01.org/0day-ci/archive/20240409/202404090849.mgj3z0xi-...@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240409/202404090849.mgj3z0xi-...@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/202404090849.mgj3z0xi-...@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/sysctl.c:1819:35: warning: initialization discards 'const' qualifier
>> from pointer target type [-Wdiscarded-qualifiers]
1819 | .extra2 = _max_max,
| ^
vim +/const +1819 kernel/sysctl.c
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1617
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1618 static struct ctl_table
kern_table[] = {
^1da177e4c3f41 Linus Torvalds 2005-04-16 1619 {
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1620 .procname
= "panic",
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1621 .data
= _timeout,
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1622 .maxlen
= sizeof(int),
49f0ce5f92321c Jerome Marchand 2014-01-21 1623 .mode
= 0644,
6d4561110a3e9f Eric W. Biederman 2009-11-16 1624 .proc_handler
= proc_dointvec,
^1da177e4c3f41 Linus Torvalds 2005-04-16 1625 },
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1626 #ifdef CONFIG_PROC_SYSCTL
^1da177e4c3f41 Linus Torvalds 2005-04-16 1627 {
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1628 .procname
= "tainted",
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1629 .maxlen
= sizeof(long),
^1da177e4c3f41 Linus Torvalds 2005-04-16 1630 .mode
= 0644,
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1631 .proc_handler
= proc_taint,
^1da177e4c3f41 Linus Torvalds 2005-04-16 1632 },
2da02997e08d3e David Rientjes 2009-01-06 1633 {
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1634 .procname
= "sysctl_writes_strict",
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1635 .data
= _writes_strict,
9e3961a0979817 Prarit Bhargava 2014-12-10 1636 .maxlen
= sizeof(int),
2da02997e08d3e David Rientjes 2009-01-06 1637 .mode
= 0644,
9e3961a0979817 Prarit Bhargava 2014-12-10 1638 .proc_handler
= proc_dointvec_minmax,
78e36f3b0dae58 Xiaoming Ni 2022-01-21 1639 .extra1
= SYSCTL_NEG_ONE,
eec4844fae7c03 Matteo Croce2019-07-18 1640 .extra2
= SYSCTL_ONE,
2da02997e08d3e David Rientjes 2009-01-06 1641 },
964c9dff009189 Alexander Popov 2018-08-17 1642 #endif
1efff914afac8a Theodore Ts'o 2015-03-17 1643 {
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1644 .procname
= "print-fatal-signals",
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1645 .data
= _fatal_signals,
964c9dff009189 Alexander Popov 2018-08-17 1646 .maxlen
= sizeof(int),
1efff914afac8a Theodore Ts'o 2015-03-17 1647 .mode
= 0644,
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1648 .proc_handler
= proc_dointvec,
1efff914afac8a Theodore Ts'o 2015-03-17 1649 },
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1650 #ifdef CONFIG_SPARC
^1da177e4c3f41 Linus Torvalds 2005-04-16 1651 {
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1652 .procname
= "reboot-cmd",
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1653 .data
= reboot_command,
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1654 .maxlen
= 256,
^1da177e4c3f41 Linus Torvalds 2005-04-16 1655 .mode
= 0644,
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1656 .proc_handler
= proc_dostring,
^1da177e4c3f41 Linus Torvalds 2005-04-16 1657 },
^1da177e4c3f41 Linus Torvalds 2005-04-16 1658 {
f461d2dcd511c0 Christoph Hellwig 2020-04-24 1659 .procname
[linus:master] [filelock] c69ff40719: stress-ng.dup.ops_per_sec 1.9% improvement
Hello,
kernel test robot noticed a 1.9% improvement of stress-ng.dup.ops_per_sec on:
commit: c69ff4071935f946f1cddc59e1d36a03442ed015 ("filelock: split leases out
of struct file_lock")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
testcase: stress-ng
test machine: 64 threads 2 sockets Intel(R) Xeon(R) Gold 6346 CPU @ 3.10GHz
(Ice Lake) with 256G memory
parameters:
nr_threads: 100%
disk: 1HDD
testtime: 60s
fs: ext4
test: dup
cpufreq_governor: performance
Details are as below:
-->
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240403/202404031033.c2d3b356-oliver.s...@intel.com
=
compiler/cpufreq_governor/disk/fs/kconfig/nr_threads/rootfs/tbox_group/test/testcase/testtime:
gcc-12/performance/1HDD/ext4/x86_64-rhel-8.3/100%/debian-12-x86_64-20240206.cgz/lkp-icl-2sp8/dup/stress-ng/60s
commit:
282c30f320 ("filelock: remove temporary compatibility macros")
c69ff40719 ("filelock: split leases out of struct file_lock")
282c30f320ba2579 c69ff4071935f946f1cddc59e1d
---
%stddev %change %stddev
\ |\
195388+2.0% 199324vmstat.system.cs
1502041+1.9%1531046stress-ng.dup.ops
25032+1.9% 25516stress-ng.dup.ops_per_sec
2020-1.9% 1982stress-ng.time.system_time
176.48 +11.1% 196.06stress-ng.time.user_time
3992532+1.8%4063489
stress-ng.time.voluntary_context_switches
1.949e+10+2.3% 1.994e+10perf-stat.i.branch-instructions
1.51-3.2% 1.46perf-stat.i.cpi
9.495e+10+2.3% 9.711e+10perf-stat.i.instructions
0.67+3.6% 0.70perf-stat.i.ipc
1.51-3.4% 1.46perf-stat.overall.cpi
0.66+3.5% 0.69perf-stat.overall.ipc
198601+1.9% 202371perf-stat.ps.context-switches
16.89-3.1 13.75
perf-profile.calltrace.cycles-pp.filp_flush.filp_close.put_files_struct.do_exit.do_group_exit
24.02-2.8 21.19
perf-profile.calltrace.cycles-pp.filp_close.put_files_struct.do_exit.do_group_exit.__x64_sys_exit_group
12.92-2.7 10.25
perf-profile.calltrace.cycles-pp.locks_remove_posix.filp_flush.filp_close.put_files_struct.do_exit
33.85-2.5 31.32
perf-profile.calltrace.cycles-pp.put_files_struct.do_exit.do_group_exit.__x64_sys_exit_group.do_syscall_64
53.34-1.8 51.51
perf-profile.calltrace.cycles-pp.do_syscall_64.entry_SYSCALL_64_after_hwframe
53.34-1.8 51.51
perf-profile.calltrace.cycles-pp.entry_SYSCALL_64_after_hwframe
53.31-1.8 51.47
perf-profile.calltrace.cycles-pp.__x64_sys_exit_group.do_syscall_64.entry_SYSCALL_64_after_hwframe
53.31-1.8 51.47
perf-profile.calltrace.cycles-pp.do_group_exit.__x64_sys_exit_group.do_syscall_64.entry_SYSCALL_64_after_hwframe
54.16-1.8 52.34
perf-profile.calltrace.cycles-pp.do_exit.do_group_exit.__x64_sys_exit_group.do_syscall_64.entry_SYSCALL_64_after_hwframe
0.62+0.00.64
perf-profile.calltrace.cycles-pp.do_dentry_open.do_open.path_openat.do_filp_open.do_sys_openat2
0.74+0.00.77
perf-profile.calltrace.cycles-pp.acct_collect.do_exit.do_group_exit.__x64_sys_exit_group.do_syscall_64
0.86+0.00.89
perf-profile.calltrace.cycles-pp.do_syscall_64.entry_SYSCALL_64_after_hwframe._exit
0.86+0.00.89
perf-profile.calltrace.cycles-pp.entry_SYSCALL_64_after_hwframe._exit
0.60+0.00.63
perf-profile.calltrace.cycles-pp.rwsem_spin_on_owner.rwsem_optimistic_spin.rwsem_down_write_slowpath.down_write.anon_vma_clone
0.86+0.00.88
perf-profile.calltrace.cycles-pp.do_group_exit.__x64_sys_exit_group.do_syscall_64.entry_SYSCALL_64_after_hwframe._exit
0.86+0.00.89
perf-profile.calltrace.cycles-pp._exit
0.68+0.00.72
perf-profile.calltrace.cycles-pp.do_open.path_openat.do_filp_open.do_sys_openat2.__x64_sys_openat
0.82+0.00.86
perf-profile.calltrace.cycles-pp.up_write.free_pgtables.exit_mmap.__mmput.exit_mm
0.70 ± 2% +0.00.74
Re: [PATCH 7/9] mm: Free up PG_slab
Hello,
kernel test robot noticed "UBSAN:shift-out-of-bounds_in_fs/proc/page.c" on:
commit: 30e5296811312a13938b83956a55839ac1e3aa40 ("[PATCH 7/9] mm: Free up
PG_slab")
url:
https://github.com/intel-lab-lkp/linux/commits/Matthew-Wilcox-Oracle/mm-Always-initialise-folio-_deferred_list/20240321-222800
base: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git
23956900041d968f9ad0f30db6dede4daccd7aa9
patch link:
https://lore.kernel.org/all/20240321142448.1645400-8-wi...@infradead.org/
patch subject: [PATCH 7/9] mm: Free up PG_slab
in testcase: ltp
version: ltp-x86_64-14c1f76-1_20240323
with following parameters:
disk: 1HDD
fs: ext4
test: fs-00
compiler: gcc-12
test machine: 4 threads 1 sockets Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz (Ivy
Bridge) with 8G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
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-lkp/202403312344.c0d273ab-oliver.s...@intel.com
kern :warn : [ 528.627387] [ cut here ]
kern :err : [ 528.627589] UBSAN: shift-out-of-bounds in
fs/proc/page.c:107:18
kern :err : [ 528.627884] shift exponent 4096 is too large for 64-bit type
'long long unsigned int'
kern :warn : [ 528.628200] CPU: 0 PID: 4703 Comm: proc01 Tainted: G S
6.8.0-11774-g30e529681131 #1
kern :warn : [ 528.628446] Hardware name: Hewlett-Packard p6-1451cx/2ADA,
BIOS 8.15 02/05/2013
kern :warn : [ 528.628659] Call Trace:
kern :warn : [ 528.628814]
kern :warn : [ 528.628960] dump_stack_lvl (lib/dump_stack.c:117 (discriminator
1))
kern :warn : [ 528.629134] __ubsan_handle_shift_out_of_bounds (lib/ubsan.c:218
lib/ubsan.c:454)
kern :warn : [ 528.629360] stable_page_flags.part.0.cold
(include/linux/page-flags.h:284 fs/proc/page.c:184)
kern :warn : [ 528.629506] kpageflags_read (fs/proc/page.c:238
fs/proc/page.c:250)
kern :warn : [ 528.629623] vfs_read (fs/read_write.c:474)
kern :warn : [ 528.629737] ? do_sys_openat2 (fs/open.c:1415)
kern :warn : [ 528.629898] ? kmem_cache_free (mm/slub.c:4280 mm/slub.c:4344)
kern :warn : [ 528.630063] ? __pfx_vfs_read (fs/read_write.c:457)
kern :warn : [ 528.630225] ? do_sys_openat2 (fs/open.c:1415)
kern :warn : [ 528.630388] ? __pfx_do_sys_openat2 (fs/open.c:1392)
kern :warn : [ 528.630552] ? __do_sys_newfstatat (fs/stat.c:464)
kern :warn : [ 528.630717] ? __fget_light
(include/linux/atomic/atomic-arch-fallback.h:479
include/linux/atomic/atomic-instrumented.h:50 fs/file.c:1145)
kern :warn : [ 528.630888] ksys_read (fs/read_write.c:619)
kern :warn : [ 528.631051] ? __pfx_ksys_read (fs/read_write.c:609)
kern :warn : [ 528.631216] ? kmem_cache_free (mm/slub.c:4280 mm/slub.c:4344)
kern :warn : [ 528.631415] do_syscall_64 (arch/x86/entry/common.c:52
arch/x86/entry/common.c:83)
kern :warn : [ 528.631555] entry_SYSCALL_64_after_hwframe
(arch/x86/entry/entry_64.S:129)
kern :warn : [ 528.631756] RIP: 0033:0x7f90bf2ba19d
kern :warn : [ 528.631913] Code: 31 c0 e9 c6 fe ff ff 50 48 8d 3d 66 54 0a 00
e8 49 ff 01 00 66 0f 1f 84 00 00 00 00 00 80 3d 41 24 0e 00 00 74 17 31 c0 0f
05 <48> 3d 00 f0 ff ff 77 5b c3 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec
All code
0: 31 c0 xor%eax,%eax
2: e9 c6 fe ff ff jmpq 0xfecd
7: 50 push %rax
8: 48 8d 3d 66 54 0a 00lea0xa5466(%rip),%rdi# 0xa5475
f: e8 49 ff 01 00 callq 0x1ff5d
14: 66 0f 1f 84 00 00 00nopw 0x0(%rax,%rax,1)
1b: 00 00
1d: 80 3d 41 24 0e 00 00cmpb $0x0,0xe2441(%rip)# 0xe2465
24: 74 17 je 0x3d
26: 31 c0 xor%eax,%eax
28: 0f 05 syscall
2a:* 48 3d 00 f0 ff ff cmp$0xf000,%rax <--
trapping instruction
30: 77 5b ja 0x8d
32: c3 retq
33: 66 2e 0f 1f 84 00 00nopw %cs:0x0(%rax,%rax,1)
3a: 00 00 00
3d: 48 rex.W
3e: 83 .byte 0x83
3f: ec in (%dx),%al
Code starting with the faulting instruction
===
0: 48 3d 00 f0 ff ff cmp$0xf000,%rax
6: 77 5b ja 0x63
8: c3 retq
9: 66 2e 0f 1f 84 00 00nopw %cs:0x0(%rax,%rax,1)
10: 00 00 00
13: 48 rex.W
14: 83 .byte 0x83
15: ec in (%dx),%al
kern :warn : [ 528.632309] RSP: 002b:7ffe2eb3c008 EFLAGS: 0246
ORIG_RAX:
kern :warn : [ 528.632540] RAX: ffda RBX: 7ffe2eb3d1b0 RCX:
Re: [PATCH v4 1/4] remoteproc: Add TEE support
Hi Arnaud,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 62210f7509e13a2caa7b080722a45229b8f17a0a]
url:
https://github.com/intel-lab-lkp/linux/commits/Arnaud-Pouliquen/remoteproc-Add-TEE-support/20240308-225116
base: 62210f7509e13a2caa7b080722a45229b8f17a0a
patch link:
https://lore.kernel.org/r/20240308144708.62362-2-arnaud.pouliquen%40foss.st.com
patch subject: [PATCH v4 1/4] remoteproc: Add TEE support
config: arm-randconfig-r123-20240310
(https://download.01.org/0day-ci/archive/20240310/202403101139.nizjmqwp-...@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0
reproduce:
(https://download.01.org/0day-ci/archive/20240310/202403101139.nizjmqwp-...@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/202403101139.nizjmqwp-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/remoteproc/tee_remoteproc.c:163:19: sparse: sparse: incorrect type
>> in assignment (different address spaces) @@ expected struct
>> resource_table *rsc_table @@ got void [noderef] __iomem * @@
drivers/remoteproc/tee_remoteproc.c:163:19: sparse: expected struct
resource_table *rsc_table
drivers/remoteproc/tee_remoteproc.c:163:19: sparse: got void [noderef]
__iomem *
>> drivers/remoteproc/tee_remoteproc.c:276:23: sparse: sparse: incorrect type
>> in argument 1 (different address spaces) @@ expected void volatile
>> [noderef] __iomem *io_addr @@ got struct resource_table *rsc_table @@
drivers/remoteproc/tee_remoteproc.c:276:23: sparse: expected void
volatile [noderef] __iomem *io_addr
drivers/remoteproc/tee_remoteproc.c:276:23: sparse: got struct
resource_table *rsc_table
drivers/remoteproc/tee_remoteproc.c:399:38: sparse: sparse: incorrect type
in argument 1 (different address spaces) @@ expected void volatile
[noderef] __iomem *io_addr @@ got struct resource_table *rsc_table @@
drivers/remoteproc/tee_remoteproc.c:399:38: sparse: expected void
volatile [noderef] __iomem *io_addr
drivers/remoteproc/tee_remoteproc.c:399:38: sparse: got struct
resource_table *rsc_table
drivers/remoteproc/tee_remoteproc.c: note: in included file (through
arch/arm/include/asm/traps.h, arch/arm/include/asm/thread_info.h,
include/linux/thread_info.h, ...):
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates
to true
vim +163 drivers/remoteproc/tee_remoteproc.c
131
132 struct resource_table *tee_rproc_get_loaded_rsc_table(struct rproc
*rproc, size_t *table_sz)
133 {
134 struct tee_ioctl_invoke_arg arg;
135 struct tee_param param[MAX_TEE_PARAM_ARRY_MEMBER];
136 struct tee_rproc *trproc = rproc->tee_interface;
137 struct resource_table *rsc_table;
138 int ret;
139
140 if (!trproc)
141 return ERR_PTR(-EINVAL);
142
143 tee_rproc_prepare_args(trproc, TA_RPROC_FW_CMD_GET_RSC_TABLE,
, param, 2);
144
145 param[1].attr = TEE_IOCTL_PARAM_ATTR_TYPE_VALUE_OUTPUT;
146 param[2].attr = TEE_IOCTL_PARAM_ATTR_TYPE_VALUE_OUTPUT;
147
148 ret = tee_client_invoke_func(tee_rproc_ctx->tee_ctx, ,
param);
149 if (ret < 0 || arg.ret != 0) {
150 dev_err(tee_rproc_ctx->dev,
151 "TA_RPROC_FW_CMD_GET_RSC_TABLE invoke failed
TEE err: %x, ret:%x\n",
152 arg.ret, ret);
153 return ERR_PTR(-EIO);
154 }
155
156 *table_sz = param[2].u.value.a;
157
158 /* If the size is null no resource table defined in the image */
159 if (!*table_sz)
160 return NULL;
161
162 /* Store the resource table address that would be updated by
the remote core. */
> 163 rsc_table = ioremap_wc(param[1].u.value.a, *table_sz);
164 if (IS_ERR_OR_NULL(rsc_table)) {
165 dev_err(tee_rproc_ctx->dev, "Unable to map memory
region: %lld+%zx\n",
166 param[1].u.value.a, *table_sz);
167 return ERR_PTR(-ENOMEM);
168 }
169
170 return rsc_table;
171 }
172 EXPORT_SYMBOL_GPL(tee_rproc_get_loaded_rsc_table);
173
174 int tee_rproc_parse_fw(struct rproc *rproc, const struct firmware *fw)
175 {
176 struct tee_rproc *trproc = rproc->tee_interface;
177 struct resource_table *rsc_table;
178 size_t table_sz;
179 int ret;
180
181 ret = tee_rproc_load_fw(rproc, fw);
182 if (ret)
183 re
Re: [PATCH 8/8] ring-buffer: Validate boot range memory events
Hi Steven,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20240305]
[cannot apply to tip/x86/core akpm-mm/mm-everything linus/master v6.8-rc7
v6.8-rc6 v6.8-rc5 v6.8-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#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Steven-Rostedt/ring-buffer-Allow-mapped-field-to-be-set-without-mapping/20240306-100047
base: next-20240305
patch link:https://lore.kernel.org/r/20240306020006.586558735%40goodmis.org
patch subject: [PATCH 8/8] ring-buffer: Validate boot range memory events
config: microblaze-allmodconfig
(https://download.01.org/0day-ci/archive/20240308/202403082327.siourqxy-...@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240308/202403082327.siourqxy-...@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/202403082327.siourqxy-...@intel.com/
All error/warnings (new ones prefixed by >>):
kernel/trace/ring_buffer.c: In function 'rb_read_data_buffer':
>> kernel/trace/ring_buffer.c:1629:29: error: 'cpu_buffer' undeclared (first
>> use in this function)
1629 | atomic_inc(_buffer->record_disabled);
\
| ^~
kernel/trace/ring_buffer.c:1667:33: note: in expansion of macro
'buffer_warn_return'
1667 | buffer_warn_return("[CPU:
%d]ABSOLUTE TIME WENT BACKWARDS: last ts: %lld absolute ts: %lld\n",
| ^~
kernel/trace/ring_buffer.c:1629:29: note: each undeclared identifier is
reported only once for each function it appears in
1629 | atomic_inc(_buffer->record_disabled);
\
| ^~
kernel/trace/ring_buffer.c:1667:33: note: in expansion of macro
'buffer_warn_return'
1667 | buffer_warn_return("[CPU:
%d]ABSOLUTE TIME WENT BACKWARDS: last ts: %lld absolute ts: %lld\n",
| ^~
>> kernel/trace/ring_buffer.c:1631:17: error: implicit declaration of function
>> 'dump_buffer_page'; did you mean 'free_buffer_page'?
>> [-Werror=implicit-function-declaration]
1631 | dump_buffer_page(bpage, info, tail);
\
| ^~~~
kernel/trace/ring_buffer.c:1667:33: note: in expansion of macro
'buffer_warn_return'
1667 | buffer_warn_return("[CPU:
%d]ABSOLUTE TIME WENT BACKWARDS: last ts: %lld absolute ts: %lld\n",
| ^~
>> kernel/trace/ring_buffer.c:1631:34: error: 'bpage' undeclared (first use in
>> this function); did you mean 'dpage'?
1631 | dump_buffer_page(bpage, info, tail);
\
| ^
kernel/trace/ring_buffer.c:1667:33: note: in expansion of macro
'buffer_warn_return'
1667 | buffer_warn_return("[CPU:
%d]ABSOLUTE TIME WENT BACKWARDS: last ts: %lld absolute ts: %lld\n",
| ^~
>> kernel/trace/ring_buffer.c:1631:41: error: 'info' undeclared (first use in
>> this function)
1631 | dump_buffer_page(bpage, info, tail);
\
| ^~~~
kernel/trace/ring_buffer.c:1667:33: note: in expansion of macro
'buffer_warn_return'
1667 | buffer_warn_return("[CPU:
%d]ABSOLUTE TIME WENT BACKWARDS: last ts: %lld absolute ts: %lld\n",
| ^~
>> kernel/trace/ring_buffer.c:1636:25: warning: 'return' with no value, in
>> function returning non-void [-Wreturn-type]
1636 | return;
\
| ^~
kernel/trace/ring_buffer.c:1667:33: note: in expansion of macro
'buffer_warn_return'
1667 | buffer_warn_return("[CPU:
%d]ABSOLUTE TIME WENT BACKWARDS: last ts: %lld absolute ts: %lld\n",
| ^~
kernel/trace/ring_buffer.c:1642:12: note: declared here
1642 | static int rb_read_data_buffer(struct buffer_data_page *dpage, int
tail,
Re: [PATCH 5/8] ring-buffer: Add ring_buffer_meta data
Hi Steven,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20240305]
[cannot apply to tip/x86/core akpm-mm/mm-everything linus/master v6.8-rc7
v6.8-rc6 v6.8-rc5 v6.8-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#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Steven-Rostedt/ring-buffer-Allow-mapped-field-to-be-set-without-mapping/20240306-100047
base: next-20240305
patch link:https://lore.kernel.org/r/20240306020006.100449500%40goodmis.org
patch subject: [PATCH 5/8] ring-buffer: Add ring_buffer_meta data
config: s390-defconfig
(https://download.01.org/0day-ci/archive/20240308/202403081843.qykjkyk4-...@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project
503c55e17037436dcd45ac69dea8967e67e3f5e8)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240308/202403081843.qykjkyk4-...@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/202403081843.qykjkyk4-...@intel.com/
All errors (new ones prefixed by >>):
In file included from kernel/trace/ring_buffer.c:8:
In file included from include/linux/trace_events.h:6:
In file included from include/linux/ring_buffer.h:5:
In file included from include/linux/mm.h:2208:
include/linux/vmstat.h:508:43: warning: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Wenum-enum-conversion]
508 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
509 |item];
|
include/linux/vmstat.h:515:43: warning: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Wenum-enum-conversion]
515 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
516 |NR_VM_NUMA_EVENT_ITEMS +
|~~
include/linux/vmstat.h:522:36: warning: arithmetic between different
enumeration types ('enum node_stat_item' and 'enum lru_list')
[-Wenum-enum-conversion]
522 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~ ^ ~~~
include/linux/vmstat.h:527:43: warning: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Wenum-enum-conversion]
527 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
528 |NR_VM_NUMA_EVENT_ITEMS +
|~~
include/linux/vmstat.h:536:43: warning: arithmetic between different
enumeration types ('enum zone_stat_item' and 'enum numa_stat_item')
[-Wenum-enum-conversion]
536 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
|~ ^
537 |NR_VM_NUMA_EVENT_ITEMS +
|~~
In file included from kernel/trace/ring_buffer.c:8:
In file included from include/linux/trace_events.h:10:
In file included from include/linux/perf_event.h:62:
In file included from include/linux/security.h:35:
include/linux/bpf.h:736:48: warning: bitwise operation between different
enumeration types ('enum bpf_type_flag' and 'enum bpf_arg_type')
[-Wenum-enum-conversion]
736 | ARG_PTR_TO_MAP_VALUE_OR_NULL= PTR_MAYBE_NULL |
ARG_PTR_TO_MAP_VALUE,
| ~~ ^
include/linux/bpf.h:737:43: warning: bitwise operation between different
enumeration types ('enum bpf_type_flag' and 'enum bpf_arg_type')
[-Wenum-enum-conversion]
737 | ARG_PTR_TO_MEM_OR_NULL = PTR_MAYBE_NULL |
ARG_PTR_TO_MEM,
| ~~ ^
~~
include/linux/bpf.h:738:43: warning: bitwise operation between different
enumeration types ('enum bpf_type_flag' and 'enum bpf_arg_type')
[-Wenum-enum-conversion]
738 | ARG_PTR_TO_CTX_OR_NULL = PTR_MAYBE_NULL |
ARG_PTR_TO_CTX,
| ~~ ^
~~
include/linux/bpf.h:739:45: warning: bitwise operation between different
enumeration types ('enum bpf_type_flag' and 'enum bpf_arg_type')
[-Wenum-enum-conv
Re: [PATCH 5/8] ring-buffer: Add ring_buffer_meta data
Hi Steven,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20240305]
[cannot apply to tip/x86/core akpm-mm/mm-everything linus/master v6.8-rc7
v6.8-rc6 v6.8-rc5 v6.8-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#_base_tree_information]
url:
https://github.com/intel-lab-lkp/linux/commits/Steven-Rostedt/ring-buffer-Allow-mapped-field-to-be-set-without-mapping/20240306-100047
base: next-20240305
patch link:https://lore.kernel.org/r/20240306020006.100449500%40goodmis.org
patch subject: [PATCH 5/8] ring-buffer: Add ring_buffer_meta data
config: sh-defconfig
(https://download.01.org/0day-ci/archive/20240308/202403081831.ewsqpo2a-...@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240308/202403081831.ewsqpo2a-...@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/202403081831.ewsqpo2a-...@intel.com/
All warnings (new ones prefixed by >>):
kernel/trace/ring_buffer.c: In function 'rb_set_commit_to_write':
>> kernel/trace/ring_buffer.c:3224:45: warning: assignment to 'long unsigned
>> int' from 'struct buffer_data_page *' makes integer from pointer without a
>> cast [-Wint-conversion]
3224 | meta->commit_buffer =
cpu_buffer->commit_page->page;
| ^
vim +3224 kernel/trace/ring_buffer.c
3192
3193 static __always_inline void
3194 rb_set_commit_to_write(struct ring_buffer_per_cpu *cpu_buffer)
3195 {
3196 unsigned long max_count;
3197
3198 /*
3199 * We only race with interrupts and NMIs on this CPU.
3200 * If we own the commit event, then we can commit
3201 * all others that interrupted us, since the interruptions
3202 * are in stack format (they finish before they come
3203 * back to us). This allows us to do a simple loop to
3204 * assign the commit to the tail.
3205 */
3206 again:
3207 max_count = cpu_buffer->nr_pages * 100;
3208
3209 while (cpu_buffer->commit_page !=
READ_ONCE(cpu_buffer->tail_page)) {
3210 if (RB_WARN_ON(cpu_buffer, !(--max_count)))
3211 return;
3212 if (RB_WARN_ON(cpu_buffer,
3213
rb_is_reader_page(cpu_buffer->tail_page)))
3214 return;
3215 /*
3216 * No need for a memory barrier here, as the update
3217 * of the tail_page did it for this page.
3218 */
3219 local_set(_buffer->commit_page->page->commit,
3220rb_page_write(cpu_buffer->commit_page));
3221 rb_inc_page(_buffer->commit_page);
3222 if (cpu_buffer->ring_meta) {
3223 struct ring_buffer_meta *meta =
cpu_buffer->ring_meta;
> 3224 meta->commit_buffer =
> cpu_buffer->commit_page->page;
3225 }
3226 /* add barrier to keep gcc from optimizing too much */
3227 barrier();
3228 }
3229 while (rb_commit_index(cpu_buffer) !=
3230 rb_page_write(cpu_buffer->commit_page)) {
3231
3232 /* Make sure the readers see the content of what is
committed. */
3233 smp_wmb();
3234 local_set(_buffer->commit_page->page->commit,
3235rb_page_write(cpu_buffer->commit_page));
3236 RB_WARN_ON(cpu_buffer,
3237
local_read(_buffer->commit_page->page->commit) &
3238 ~RB_WRITE_MASK);
3239 barrier();
3240 }
3241
3242 /* again, keep gcc from optimizing */
3243 barrier();
3244
3245 /*
3246 * If an interrupt came in just after the first while loop
3247 * and pushed the tail page forward, we will be left with
3248 * a dangling commit that will never go forward.
3249 */
3250 if (unlikely(cpu_buffer->commit_page !=
READ_ONCE(cpu_buffer->tail_page)))
3251 goto again;
3252 }
3253
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH net-next v2 3/3] tun: AF_XDP Tx zero-copy support
Hi Yunjian,
kernel test robot noticed the following build errors:
[auto build test ERROR on net-next/main]
url:
https://github.com/intel-lab-lkp/linux/commits/Yunjian-Wang/xsk-Remove-non-zero-dma_page-check-in-xp_assign_dev/20240228-190840
base: net-next/main
patch link:
https://lore.kernel.org/r/1709118356-133960-1-git-send-email-wangyunjian%40huawei.com
patch subject: [PATCH net-next v2 3/3] tun: AF_XDP Tx zero-copy support
config: microblaze-randconfig-r131-20240229
(https://download.01.org/0day-ci/archive/20240229/202402292345.a49gfjlj-...@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 13.2.0
reproduce:
(https://download.01.org/0day-ci/archive/20240229/202402292345.a49gfjlj-...@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/202402292345.a49gfjlj-...@intel.com/
All errors (new ones prefixed by >>):
drivers/vhost/net.c: In function 'vhost_net_buf_peek_len':
>> drivers/vhost/net.c:206:41: error: initialization of 'struct xdp_desc *'
>> from incompatible pointer type 'struct xdp_frame *'
>> [-Werror=incompatible-pointer-types]
206 | struct xdp_desc *desc = tun_ptr_to_xdp_desc(ptr);
| ^~~
cc1: some warnings being treated as errors
vim +206 drivers/vhost/net.c
198
199 static int vhost_net_buf_peek_len(void *ptr)
200 {
201 if (tun_is_xdp_frame(ptr)) {
202 struct xdp_frame *xdpf = tun_ptr_to_xdp(ptr);
203
204 return xdpf->len;
205 } else if (tun_is_xdp_desc_frame(ptr)) {
> 206 struct xdp_desc *desc = tun_ptr_to_xdp_desc(ptr);
207
208 return desc->len;
209 }
210
211 return __skb_array_len_with_tag(ptr);
212 }
213
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[mhiramat:topic/fprobe-on-fgraph] [function_graph] ab712273e5: WARNING:at_kernel/trace/trace.c:#run_tracer_selftest
Hello,
kernel test robot noticed
"WARNING:at_kernel/trace/trace.c:#run_tracer_selftest" on:
commit: ab712273e5b93b2162bd25823c50afa067c971d7 ("function_graph: Pass
ftrace_regs to entryfunc")
https://git.kernel.org/cgit/linux/kernel/git/mhiramat/linux.git
topic/fprobe-on-fgraph
in testcase: boot
compiler: gcc-11
test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+-+++
| | 18e3163a72 |
ab712273e5 |
+-+++
| WARNING:at_kernel/trace/trace.c:#run_tracer_selftest| 0 | 17
|
| EIP:run_tracer_selftest | 0 | 17
|
+-+++
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-lkp/202402292204.c1f77860-oliver.s...@intel.com
[9.224340][T1] [ cut here ]
[ 9.225209][ T1] WARNING: CPU: 1 PID: 1 at kernel/trace/trace.c:2053
run_tracer_selftest (kernel/trace/trace.c:2053 (discriminator 1))
[9.226920][T1] Modules linked in:
[9.227542][T1] CPU: 1 PID: 1 Comm: swapper/0 Not tainted
6.8.0-rc4-00021-gab712273e5b9 #1 b22c8cda139bb32aef1f09ba4b94f28d718abc25
[9.229490][T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 9.230911][ T1] EIP: run_tracer_selftest (kernel/trace/trace.c:2053
(discriminator 1))
[ 9.231772][ T1] Code: 00 00 00 00 8b 15 5c 14 27 c3 b9 ff ff ff ff a1 a8 14 27
c3 e8 23 60 ff ff e9 8c fe ff ff c7 04 24 c3 18 ca c2 e8 ea 9d f4 ff <0f> 0b be
ff ff ff ff e9 60 ff ff ff be f4 ff ff ff e9 56 ff ff ff
All code
0: 00 00 add%al,(%rax)
2: 00 00 add%al,(%rax)
4: 8b 15 5c 14 27 c3 mov-0x3cd8eba4(%rip),%edx#
0xc3271466
a: b9 ff ff ff ff mov$0x,%ecx
f: a1 a8 14 27 c3 e8 23movabs 0xff6023e8c32714a8,%eax
16: 60 ff
18: ff (bad)
19: e9 8c fe ff ff jmp0xfeaa
1e: c7 04 24 c3 18 ca c2movl $0xc2ca18c3,(%rsp)
25: e8 ea 9d f4 ff call 0xfff49e14
2a:* 0f 0b ud2 <-- trapping instruction
2c: be ff ff ff ff mov$0x,%esi
31: e9 60 ff ff ff jmp0xff96
36: be f4 ff ff ff mov$0xfff4,%esi
3b: e9 56 ff ff ff jmp0xff96
Code starting with the faulting instruction
===
0: 0f 0b ud2
2: be ff ff ff ff mov$0x,%esi
7: e9 60 ff ff ff jmp0xff6c
c: be f4 ff ff ff mov$0xfff4,%esi
11: e9 56 ff ff ff jmp0xff6c
[9.234972][T1] EAX: 0007 EBX: c34453a0 ECX: EDX:
[9.234972][T1] ESI: EDI: c3479760 EBP: c4c47e84 ESP: c4c47e70
[9.236035][T1] DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 EFLAGS:
00010246
[9.237240][T1] CR0: 80050033 CR2: CR3: 03739000 CR4: 000406d0
[9.238361][T1] Call Trace:
[ 9.238877][ T1] ? show_regs (arch/x86/kernel/dumpstack.c:479)
[ 9.238912][ T1] ? run_tracer_selftest (kernel/trace/trace.c:2053
(discriminator 1))
[ 9.239756][ T1] ? __warn (kernel/panic.c:677)
[ 9.240397][ T1] ? run_tracer_selftest (kernel/trace/trace.c:2053
(discriminator 1))
[ 9.241233][ T1] ? run_tracer_selftest (kernel/trace/trace.c:2053
(discriminator 1))
[ 9.242070][ T1] ? report_bug (lib/bug.c:201 lib/bug.c:219)
[ 9.242782][ T1] ? exc_overflow (arch/x86/kernel/traps.c:251)
[ 9.242911][ T1] ? handle_bug (arch/x86/kernel/traps.c:238)
[ 9.243607][ T1] ? exc_invalid_op (arch/x86/kernel/traps.c:259 (discriminator
1))
[ 9.244341][ T1] ? __wake_up_klogd+0x49/0x70
[ 9.245189][ T1] ? preempt_count_sub (kernel/sched/core.c:5881
kernel/sched/core.c:5877 kernel/sched/core.c:5899)
[ 9.245969][ T1] ? handle_exception (arch/x86/entry/entry_32.S:1056)
[ 9.246767][ T1] ? exc_overflow (arch/x86/kernel/traps.c:251)
[ 9.250912][ T1] ? run_tracer_selftest (kernel/trace/trace.c:2053
(discriminator 1))
[ 9.251749][ T1] ? exc_overflow (arch/x86/kernel/traps.c:251)
[ 9.252458][ T1] ? run_tracer_selftest (kernel/trace/trace.c:2053
(discriminator 1))
[ 9.253288][ T1] ? graph_depth_read (kernel/trace/trace_functions_graph.c:1349)
[ 9.254057][ T1] register_tracer (kernel/trace/trace.c:2086
kernel/trace/t
Re: [PATCH net-next v2 3/3] tun: AF_XDP Tx zero-copy support
Hi Yunjian,
kernel test robot noticed the following build errors:
[auto build test ERROR on net-next/main]
url:
https://github.com/intel-lab-lkp/linux/commits/Yunjian-Wang/xsk-Remove-non-zero-dma_page-check-in-xp_assign_dev/20240228-190840
base: net-next/main
patch link:
https://lore.kernel.org/r/1709118356-133960-1-git-send-email-wangyunjian%40huawei.com
patch subject: [PATCH net-next v2 3/3] tun: AF_XDP Tx zero-copy support
config: i386-randconfig-012-20240229
(https://download.01.org/0day-ci/archive/20240229/202402291828.g9c5tw50-...@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240229/202402291828.g9c5tw50-...@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/202402291828.g9c5tw50-...@intel.com/
All errors (new ones prefixed by >>):
drivers/vhost/net.c: In function 'vhost_net_buf_peek_len':
>> drivers/vhost/net.c:206:27: error: initialization from incompatible pointer
>> type [-Werror=incompatible-pointer-types]
struct xdp_desc *desc = tun_ptr_to_xdp_desc(ptr);
^~~
cc1: some warnings being treated as errors
vim +206 drivers/vhost/net.c
198
199 static int vhost_net_buf_peek_len(void *ptr)
200 {
201 if (tun_is_xdp_frame(ptr)) {
202 struct xdp_frame *xdpf = tun_ptr_to_xdp(ptr);
203
204 return xdpf->len;
205 } else if (tun_is_xdp_desc_frame(ptr)) {
> 206 struct xdp_desc *desc = tun_ptr_to_xdp_desc(ptr);
207
208 return desc->len;
209 }
210
211 return __skb_array_len_with_tag(ptr);
212 }
213
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v17 2/6] ring-buffer: Introducing ring-buffer mapping functions
Hi Vincent, kernel test robot noticed the following build errors: [auto build test ERROR on ca185770db914869ff9fe773bac5e0e5e4165b83] url: https://github.com/intel-lab-lkp/linux/commits/Vincent-Donnefort/ring-buffer-Zero-ring-buffer-sub-buffers/20240213-195302 base: ca185770db914869ff9fe773bac5e0e5e4165b83 patch link: https://lore.kernel.org/r/20240213114945.3528801-3-vdonnefort%40google.com patch subject: [PATCH v17 2/6] ring-buffer: Introducing ring-buffer mapping functions config: x86_64-randconfig-161-20240214 (https://download.01.org/0day-ci/archive/20240214/202402141856.fvl4pchi-...@intel.com/config) compiler: gcc-9 (Debian 9.3.0-22) 9.3.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240214/202402141856.fvl4pchi-...@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/202402141856.fvl4pchi-...@intel.com/ All errors (new ones prefixed by >>): In file included from arch/x86/include/asm/bug.h:87, from include/linux/bug.h:5, from include/linux/jump_label.h:256, from arch/x86/include/asm/string_64.h:6, from arch/x86/include/asm/string.h:5, from include/linux/string.h:61, from include/linux/bitmap.h:12, from include/linux/cpumask.h:12, from include/linux/interrupt.h:8, from include/linux/trace_recursion.h:5, from kernel/trace/ring_buffer.c:7: kernel/trace/ring_buffer.c: In function '__rb_inc_dec_mapped': >> include/linux/lockdep.h:234:52: error: invalid type argument of '->' (have >> 'struct mutex') 234 | #define lockdep_is_held(lock) lock_is_held(&(lock)->dep_map) |^~ include/asm-generic/bug.h:123:25: note: in definition of macro 'WARN_ON' 123 | int __ret_warn_on = !!(condition);\ | ^ include/linux/lockdep.h:267:2: note: in expansion of macro 'lockdep_assert' 267 | lockdep_assert(lockdep_is_held(l) != LOCK_STATE_NOT_HELD) | ^~ include/linux/lockdep.h:267:17: note: in expansion of macro 'lockdep_is_held' 267 | lockdep_assert(lockdep_is_held(l) != LOCK_STATE_NOT_HELD) | ^~~ kernel/trace/ring_buffer.c:6185:2: note: in expansion of macro 'lockdep_assert_held' 6185 | lockdep_assert_held(cpu_buffer->mapping_lock); | ^~~ vim +234 include/linux/lockdep.h f607c668577481 Peter Zijlstra 2009-07-20 233 f8319483f57f1c Peter Zijlstra 2016-11-30 @234 #define lockdep_is_held(lock) lock_is_held(&(lock)->dep_map) f8319483f57f1c Peter Zijlstra 2016-11-30 235 #define lockdep_is_held_type(lock, r)lock_is_held_type(&(lock)->dep_map, (r)) f607c668577481 Peter Zijlstra 2009-07-20 236 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 1/4] tracing/user_events: Prepare find/delete for same name events
Hello,
kernel test robot noticed "BUG:KASAN:slab-use-after-free_in_user_events_ioctl"
on:
commit: fecc001d587ceeeb47043c20353f257e3f01b39f ("[PATCH v2 1/4]
tracing/user_events: Prepare find/delete for same name events")
url:
https://github.com/intel-lab-lkp/linux/commits/Beau-Belgrave/tracing-user_events-Prepare-find-delete-for-same-name-events/20240203-031207
patch link:
https://lore.kernel.org/all/20240202184449.1674-2-be...@linux.microsoft.com/
patch subject: [PATCH v2 1/4] tracing/user_events: Prepare find/delete for same
name events
in testcase: kernel-selftests
version: kernel-selftests-x86_64-60acb023-1_20230329
with following parameters:
group: user_events
compiler: gcc-12
test machine: 36 threads 1 sockets Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz
(Cascade Lake) with 32G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
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-lkp/202402141240.cc5aba78-oliver.s...@intel.com
[ 106.969333][ T2278] BUG: KASAN: slab-use-after-free in user_events_ioctl
(kernel/trace/trace_events_user.c:2067 kernel/trace/trace_events_user.c:2401
kernel/trace/trace_events_user.c:2543)
[ 106.970079][ T2278] Read of size 8 at addr 88816644ef38 by task
abi_test/2278
[ 106.970788][ T2278]
[ 106.971058][ T2278] CPU: 2 PID: 2278 Comm: abi_test Not tainted
6.7.0-rc8-1-gfecc001d587c #1
[ 106.971881][ T2278] Hardware name: Gigabyte Technology Co., Ltd. X299 UD4
Pro/X299 UD4 Pro-CF, BIOS F8a 04/27/2021
[ 106.972829][ T2278] Call Trace:
[ 106.973185][ T2278]
[ 106.973514][ T2278] dump_stack_lvl (lib/dump_stack.c:108)
[ 106.973966][ T2278] print_address_description+0x2c/0x3a0
[ 106.974597][ T2278] ? user_events_ioctl
(kernel/trace/trace_events_user.c:2067 kernel/trace/trace_events_user.c:2401
kernel/trace/trace_events_user.c:2543)
[ 106.975099][ T2278] print_report (mm/kasan/report.c:476)
[ 106.975542][ T2278] ? kasan_addr_to_slab (mm/kasan/common.c:35)
[ 106.976025][ T2278] ? user_events_ioctl
(kernel/trace/trace_events_user.c:2067 kernel/trace/trace_events_user.c:2401
kernel/trace/trace_events_user.c:2543)
[ 106.976531][ T2278] kasan_report (mm/kasan/report.c:590)
[ 106.976978][ T2278] ? user_events_ioctl
(kernel/trace/trace_events_user.c:2067 kernel/trace/trace_events_user.c:2401
kernel/trace/trace_events_user.c:2543)
[ 106.977481][ T2278] user_events_ioctl (kernel/trace/trace_events_user.c:2067
kernel/trace/trace_events_user.c:2401 kernel/trace/trace_events_user.c:2543)
[ 106.977970][ T2278] __x64_sys_ioctl (fs/ioctl.c:52 fs/ioctl.c:871
fs/ioctl.c:857 fs/ioctl.c:857)
[ 106.978441][ T2278] do_syscall_64 (arch/x86/entry/common.c:52
arch/x86/entry/common.c:83)
[ 106.978889][ T2278] entry_SYSCALL_64_after_hwframe
(arch/x86/entry/entry_64.S:129)
[ 106.979462][ T2278] RIP: 0033:0x7f2e121c8b5b
[ 106.979907][ T2278] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10
00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89>
c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00
All code
0: 00 48 89add%cl,-0x77(%rax)
3: 44 24 18rex.R and $0x18,%al
6: 31 c0 xor%eax,%eax
8: 48 8d 44 24 60 lea0x60(%rsp),%rax
d: c7 04 24 10 00 00 00movl $0x10,(%rsp)
14: 48 89 44 24 08 mov%rax,0x8(%rsp)
19: 48 8d 44 24 20 lea0x20(%rsp),%rax
1e: 48 89 44 24 10 mov%rax,0x10(%rsp)
23: b8 10 00 00 00 mov$0x10,%eax
28: 0f 05 syscall
2a:* 89 c2 mov%eax,%edx<-- trapping
instruction
2c: 3d 00 f0 ff ff cmp$0xf000,%eax
31: 77 1c ja 0x4f
33: 48 8b 44 24 18 mov0x18(%rsp),%rax
38: 64 fs
39: 48 rex.W
3a: 2b .byte 0x2b
3b: 04 25 add$0x25,%al
3d: 28 00 sub%al,(%rax)
...
Code starting with the faulting instruction
===
0: 89 c2 mov%eax,%edx
2: 3d 00 f0 ff ff cmp$0xf000,%eax
7: 77 1c ja 0x25
9: 48 8b 44 24 18 mov0x18(%rsp),%rax
e: 64 fs
f: 48 rex.W
10: 2b .byte 0x2b
11: 04 25 add$0x25,%al
13: 28 00 sub%al,(%rax)
...
[ 106.981608][ T2278] RSP: 002b:7ffcb0ba5ed0 EFLAGS: 0246 ORIG_RAX:
0010
[ 106.982385][ T2278] RAX: ffda RBX: 7ffcb0ba6228 RCX:
7f2e121c8b5b
[ 106.983128][ T22
Re: [PATCH v17 2/6] ring-buffer: Introducing ring-buffer mapping functions
Hi Vincent,
kernel test robot noticed the following build errors:
[auto build test ERROR on ca185770db914869ff9fe773bac5e0e5e4165b83]
url:
https://github.com/intel-lab-lkp/linux/commits/Vincent-Donnefort/ring-buffer-Zero-ring-buffer-sub-buffers/20240213-195302
base: ca185770db914869ff9fe773bac5e0e5e4165b83
patch link:
https://lore.kernel.org/r/20240213114945.3528801-3-vdonnefort%40google.com
patch subject: [PATCH v17 2/6] ring-buffer: Introducing ring-buffer mapping
functions
config: i386-buildonly-randconfig-001-20240214
(https://download.01.org/0day-ci/archive/20240214/202402140910.tfs9k0yr-...@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project
6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240214/202402140910.tfs9k0yr-...@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/202402140910.tfs9k0yr-...@intel.com/
All errors (new ones prefixed by >>):
>> kernel/trace/ring_buffer.c:6185:2: error: member reference type 'struct
>> mutex' is not a pointer; did you mean to use '.'?
6185 | lockdep_assert_held(cpu_buffer->mapping_lock);
| ^
include/linux/lockdep.h:267:17: note: expanded from macro
'lockdep_assert_held'
267 | lockdep_assert(lockdep_is_held(l) != LOCK_STATE_NOT_HELD)
| ~~~^~
include/linux/lockdep.h:234:52: note: expanded from macro 'lockdep_is_held'
234 | #define lockdep_is_held(lock)
lock_is_held(&(lock)->dep_map)
| ^
include/linux/lockdep.h:261:32: note: expanded from macro 'lockdep_assert'
261 | do { WARN_ON(debug_locks && !(cond)); } while (0)
| ~^~
include/asm-generic/bug.h:123:25: note: expanded from macro 'WARN_ON'
123 | int __ret_warn_on = !!(condition);
\
|^
>> kernel/trace/ring_buffer.c:6185:2: error: cannot take the address of an
>> rvalue of type 'struct lockdep_map'
6185 | lockdep_assert_held(cpu_buffer->mapping_lock);
| ^
include/linux/lockdep.h:267:17: note: expanded from macro
'lockdep_assert_held'
267 | lockdep_assert(lockdep_is_held(l) != LOCK_STATE_NOT_HELD)
| ~~~^~
include/linux/lockdep.h:234:45: note: expanded from macro 'lockdep_is_held'
234 | #define lockdep_is_held(lock)
lock_is_held(&(lock)->dep_map)
| ^
include/linux/lockdep.h:261:32: note: expanded from macro 'lockdep_assert'
261 | do { WARN_ON(debug_locks && !(cond)); } while (0)
| ~^~
include/asm-generic/bug.h:123:25: note: expanded from macro 'WARN_ON'
123 | int __ret_warn_on = !!(condition);
\
|^
2 errors generated.
vim +6185 kernel/trace/ring_buffer.c
6174
6175 /*
6176 * Fast-path for rb_buffer_(un)map(). Called whenever the meta-page
doesn't need
6177 * to be set-up or torn-down.
6178 */
6179 static int __rb_inc_dec_mapped(struct trace_buffer *buffer,
6180 struct ring_buffer_per_cpu *cpu_buffer,
6181 bool inc)
6182 {
6183 unsigned long flags;
6184
> 6185 lockdep_assert_held(cpu_buffer->mapping_lock);
6186
6187 if (inc && cpu_buffer->mapped == UINT_MAX)
6188 return -EBUSY;
6189
6190 if (WARN_ON(!inc && cpu_buffer->mapped == 0))
6191 return -EINVAL;
6192
6193 mutex_lock(>mutex);
6194 raw_spin_lock_irqsave(_buffer->reader_lock, flags);
6195
6196 if (inc)
6197 cpu_buffer->mapped++;
6198 else
6199 cpu_buffer->mapped--;
6200
6201 raw_spin_unlock_irqrestore(_buffer->reader_lock, flags);
6202 mutex_unlock(>mutex);
6203
6204 return 0;
6205 }
6206
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v14 4/6] tracing: Allow user-space mapping of the ring-buffer
Hi Vincent,
kernel test robot noticed the following build warnings:
[auto build test WARNING on e2412e51fdea837b50ce31fea8e5dfc885237f3a]
url:
https://github.com/intel-lab-lkp/linux/commits/Vincent-Donnefort/ring-buffer-Zero-ring-buffer-sub-buffers/20240206-004413
base: e2412e51fdea837b50ce31fea8e5dfc885237f3a
patch link:
https://lore.kernel.org/r/20240205163410.2296552-5-vdonnefort%40google.com
patch subject: [PATCH v14 4/6] tracing: Allow user-space mapping of the
ring-buffer
config: arc-defconfig
(https://download.01.org/0day-ci/archive/20240206/202402061809.t2cv9j8w-...@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240206/202402061809.t2cv9j8w-...@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/202402061809.t2cv9j8w-...@intel.com/
All warnings (new ones prefixed by >>):
kernel/trace/trace.c: In function 'tracing_buffers_mmap_close':
>> kernel/trace/trace.c:8722:29: warning: unused variable 'tr'
>> [-Wunused-variable]
8722 | struct trace_array *tr = iter->tr;
| ^~
kernel/trace/trace.c: In function 'tracing_buffers_mmap':
kernel/trace/trace.c:8752:29: warning: unused variable 'tr'
[-Wunused-variable]
8752 | struct trace_array *tr = iter->tr;
| ^~
vim +/tr +8722 kernel/trace/trace.c
8717
8718 static void tracing_buffers_mmap_close(struct vm_area_struct *vma)
8719 {
8720 struct ftrace_buffer_info *info = vma->vm_file->private_data;
8721 struct trace_iterator *iter = >iter;
> 8722 struct trace_array *tr = iter->tr;
8723
8724 ring_buffer_unmap(iter->array_buffer->buffer, iter->cpu_file);
8725
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v3 3/3] tracing: convert __trace_seq_init to use WARN_ON_ONCE
Hello,
kernel test robot noticed
"WARNING:at_kernel/trace/trace_seq.c:#trace_seq_printf" on:
commit: 233bcd2427b36992e8918a67a88912f9c3d497af ("[PATCH v3 3/3] tracing:
convert __trace_seq_init to use WARN_ON_ONCE")
url:
https://github.com/intel-lab-lkp/linux/commits/Ricardo-B-Marliere/tracing-initialize-trace_seq-buffers/20240126-063125
base: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git
ecb1b8288dc7ccbdcb3b9df005fa1c0e0c0388a7
patch link:
https://lore.kernel.org/all/20240125222818.7425-4-rica...@marliere.net/
patch subject: [PATCH v3 3/3] tracing: convert __trace_seq_init to use
WARN_ON_ONCE
in testcase: boot
compiler: clang-17
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
we noticed the WARN_ON_ONCE added in this commit was hit in our tests. but
not always happen, just FYI.
27b32d2097dcb40a 233bcd2427b36992e8918a67a88
---
fail:runs %reproductionfail:runs
| | |
:10 50% 5:11dmesg.RIP:trace_seq_printf
:10 50% 5:11
dmesg.WARNING:at_kernel/trace/trace_seq.c:#trace_seq_printf
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-lkp/202402052141.769871e2-...@intel.com
[ 1915.506477][ T42] [ cut here ]
[ 1915.506778][ T42] WARNING: CPU: 0 PID: 42 at kernel/trace/trace_seq.c:35
trace_seq_printf (kernel/trace/trace_seq.c:35)
[ 1915.507296][ T42] Modules linked in: ipv6
[ 1915.507538][ T42] CPU: 0 PID: 42 Comm: rcu_scale_write Tainted: G
TN 6.8.0-rc1-00172-g233bcd2427b3 #1
[ 1915.508125][ T42] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 1915.508690][ T42] RIP: 0010:trace_seq_printf (kernel/trace/trace_seq.c:35)
[ 1915.508999][ T42] Code: 00 00 48 3b 83 e8 1f 00 00 77 51 48 8d 65 f0 5b 41
5e 5d 31 c0 31 c9 31 ff 31 d2 45 31 c0 45 31 c9 c3 cc 48 8d 83 f0 1f 00 00 <0f>
0b 48 89 9b e0 1f 00 00 48 c7 83 e8 1f 00 00 dc 1f 00 00 c6 03
All code
0: 00 00 add%al,(%rax)
2: 48 3b 83 e8 1f 00 00cmp0x1fe8(%rbx),%rax
9: 77 51 ja 0x5c
b: 48 8d 65 f0 lea-0x10(%rbp),%rsp
f: 5b pop%rbx
10: 41 5e pop%r14
12: 5d pop%rbp
13: 31 c0 xor%eax,%eax
15: 31 c9 xor%ecx,%ecx
17: 31 ff xor%edi,%edi
19: 31 d2 xor%edx,%edx
1b: 45 31 c0xor%r8d,%r8d
1e: 45 31 c9xor%r9d,%r9d
21: c3 ret
22: cc int3
23: 48 8d 83 f0 1f 00 00lea0x1ff0(%rbx),%rax
2a:* 0f 0b ud2 <-- trapping instruction
2c: 48 89 9b e0 1f 00 00mov%rbx,0x1fe0(%rbx)
33: 48 c7 83 e8 1f 00 00movq $0x1fdc,0x1fe8(%rbx)
3a: dc 1f 00 00
3e: c6 .byte 0xc6
3f: 03 .byte 0x3
Code starting with the faulting instruction
===
0: 0f 0b ud2
2: 48 89 9b e0 1f 00 00mov%rbx,0x1fe0(%rbx)
9: 48 c7 83 e8 1f 00 00movq $0x1fdc,0x1fe8(%rbx)
10: dc 1f 00 00
14: c6 .byte 0xc6
15: 03 .byte 0x3
[ 1915.510058][ T42] RSP: 0018:c9157d40 EFLAGS: 00010046
[ 1915.510390][ T42] RAX: 84141a18 RBX: 8413fa28 RCX:
0001
[ 1915.510822][ T42] RDX: c9157dc0 RSI: 82768da2 RDI:
84141a08
[ 1915.511253][ T42] RBP: c9157da0 R08: R09:
[ 1915.511684][ T42] R10: R11: R12:
[ 1915.512115][ T42] R13: c9157dc0 R14: R15:
8413d894
[ 1915.512546][ T42] FS: () GS:82a6()
knlGS:
[ 1915.513033][ T42] CS: 0010 DS: ES: CR0: 80050033
[ 1915.513392][ T42] CR2: 55fe70034138 CR3: 0001740d7000 CR4:
000406b0
[ 1915.513828][ T42] DR0: DR1: DR2:
[ 1915.514262][ T42] DR3: DR6: fffe0ff0 DR7:
0400
[ 1915.514696][ T42] Call Trace:
[ 1915.514881][ T42]
[ 1915.515048][ T42] ? __warn (kernel/panic.c:236 kernel/panic.c:677)
[ 1915.515275][ T42] ? trace_seq_printf (kernel/trace/trace_seq.c:35)
[ 1915.515550][ T42] ? report_bug (lib/bug.c:?)
[ 1915.515799][ T42] ? handle_bug
[kees:devel/overflow/sanitizers] [overflow] 660787b56e: UBSAN:signed-integer-overflow_in_lib/test_memcat_p.c
Hello,
kernel test robot noticed
"UBSAN:signed-integer-overflow_in_lib/test_memcat_p.c" on:
commit: 660787b56e6e97ddc34c7882cbe1228f4040ef74 ("overflow: Reintroduce signed
and unsigned overflow sanitizers")
https://git.kernel.org/cgit/linux/kernel/git/kees/linux.git
devel/overflow/sanitizers
in testcase: boot
compiler: gcc-11
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
we noticed this commit is reintroducing "signed and unsigned overflow
sanitizers", there is below config diff between parent and this commit in our
buildings:
--- ea804316c9db5148d2bb0c1f40f70d7a83404638/.config2024-01-26
22:09:35.046768122 +0800
+++ 660787b56e6e97ddc34c7882cbe1228f4040ef74/.config2024-01-26
19:53:20.693434428 +0800
@@ -6706,6 +6706,7 @@ CONFIG_UBSAN_BOUNDS_STRICT=y
CONFIG_UBSAN_SHIFT=y
# CONFIG_UBSAN_DIV_ZERO is not set
CONFIG_UBSAN_UNREACHABLE=y
+CONFIG_UBSAN_SIGNED_WRAP=y
# CONFIG_UBSAN_BOOL is not set
# CONFIG_UBSAN_ENUM is not set
# CONFIG_UBSAN_ALIGNMENT is not set
while testing, we observed below different (and same part) between parent and
this commit:
ea804316c9db5148 660787b56e6e97ddc34c7882cbe
---
fail:runs %reproductionfail:runs
| | |
6:60% 6:6
dmesg.UBSAN:shift-out-of-bounds_in_arch/x86/kernel/cpu/intel.c
6:60% 6:6
dmesg.UBSAN:shift-out-of-bounds_in_arch/x86/kernel/cpu/topology.c
6:60% 6:6
dmesg.UBSAN:shift-out-of-bounds_in_fs/namespace.c
6:60% 6:6
dmesg.UBSAN:shift-out-of-bounds_in_fs/read_write.c
6:60% 6:6
dmesg.UBSAN:shift-out-of-bounds_in_include/linux/rhashtable.h
6:60% 6:6
dmesg.UBSAN:shift-out-of-bounds_in_include/net/tcp.h
:6 100% 6:6
dmesg.UBSAN:signed-integer-overflow_in_lib/test_memcat_p.c
this looks like the commit uncovered issue. but since it's hard for us to back
port this commit to each commit while bisecting, we cannot capture the real
first bad commit. not sure if this report could help somebody to investigate
the real issue?
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-lkp/202401302219.db90a6d5-oliver.s...@intel.com
[ 42.894536][T1] [ cut here ]
[ 42.895474][T1] UBSAN: signed-integer-overflow in
lib/test_memcat_p.c:47:10
[ 42.897128][T1] 6570 * 725861 cannot be represented in type 'int'
[ 42.898391][T1] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
6.8.0-rc1-7-g660787b56e6e #1
[ 42.899962][T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 42.901661][T1] Call Trace:
[ 42.902009][ T1] dump_stack_lvl (??:?)
[ 42.902009][ T1] dump_stack (??:?)
[ 42.902009][ T1] handle_overflow (ubsan.c:?)
[ 42.902009][ T1] ? kmemleak_alloc (??:?)
[ 42.902009][ T1] ? kmalloc_trace (??:?)
[ 42.902009][ T1] ? test_memcat_p_init (test_memcat_p.c:?)
[ 42.902009][ T1] __ubsan_handle_mul_overflow (??:?)
[ 42.902009][ T1] test_memcat_p_init (test_memcat_p.c:?)
[ 42.902009][ T1] ? trace_hardirqs_on (??:?)
[ 42.902009][ T1] ? _raw_spin_unlock_irqrestore (??:?)
[ 42.902009][ T1] ? test_string_helpers_init (test_memcat_p.c:?)
[ 42.902009][ T1] do_one_initcall (??:?)
[ 42.902009][ T1] ? parameq (??:?)
[ 42.902009][ T1] ? parse_args (??:?)
[ 42.902009][ T1] do_initcalls (main.c:?)
[ 42.902009][ T1] ? rdinit_setup (main.c:?)
[ 42.902009][ T1] kernel_init_freeable (main.c:?)
[ 42.902009][ T1] ? rest_init (main.c:?)
[ 42.902009][ T1] kernel_init (main.c:?)
[ 42.902009][ T1] ? schedule_tail (??:?)
[ 42.902009][ T1] ret_from_fork (??:?)
[ 42.902009][ T1] ? rest_init (main.c:?)
[ 42.902009][ T1] ret_from_fork_asm (??:?)
[ 42.902009][ T1] entry_INT80_32 (??:?)
[ 42.924183][T1] ---[ end trace ]---
[ 42.925743][T1] test_memcat_p: test passed
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240130/202401302219.db90a6d5-oliver.s...@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v13 3/6] tracing: Add snapshot refcount
Hi Vincent,
kernel test robot noticed the following build errors:
[auto build test ERROR on 29142dc92c37d3259a33aef15b03e6ee25b0d188]
url:
https://github.com/intel-lab-lkp/linux/commits/Vincent-Donnefort/ring-buffer-Zero-ring-buffer-sub-buffers/20240129-223025
base: 29142dc92c37d3259a33aef15b03e6ee25b0d188
patch link:
https://lore.kernel.org/r/20240129142802.2145305-4-vdonnefort%40google.com
patch subject: [PATCH v13 3/6] tracing: Add snapshot refcount
config: arc-randconfig-002-20240130
(https://download.01.org/0day-ci/archive/20240130/202401301740.qzzlpcyv-...@intel.com/config)
compiler: arceb-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240130/202401301740.qzzlpcyv-...@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/202401301740.qzzlpcyv-...@intel.com/
All errors (new ones prefixed by >>):
kernel/trace/trace.c: In function 'tracing_set_tracer':
kernel/trace/trace.c:6644:17: error: implicit declaration of function
'tracing_disarm_snapshot_locked'; did you mean 'tracing_disarm_snapshot'?
[-Werror=implicit-function-declaration]
6644 | tracing_disarm_snapshot_locked(tr);
| ^~
| tracing_disarm_snapshot
>> kernel/trace/trace.c:6648:23: error: implicit declaration of function
>> 'tracing_arm_snapshot_locked'; did you mean 'tracing_arm_snapshot'?
>> [-Werror=implicit-function-declaration]
6648 | ret = tracing_arm_snapshot_locked(tr);
| ^~~
| tracing_arm_snapshot
cc1: some warnings being treated as errors
vim +6648 kernel/trace/trace.c
6560
6561 int tracing_set_tracer(struct trace_array *tr, const char *buf)
6562 {
6563 struct tracer *t;
6564 #ifdef CONFIG_TRACER_MAX_TRACE
6565 bool had_max_tr;
6566 #endif
6567 int ret = 0;
6568
6569 mutex_lock(_types_lock);
6570
6571 if (!tr->ring_buffer_expanded) {
6572 ret = __tracing_resize_ring_buffer(tr, trace_buf_size,
6573 RING_BUFFER_ALL_CPUS);
6574 if (ret < 0)
6575 goto out;
6576 ret = 0;
6577 }
6578
6579 for (t = trace_types; t; t = t->next) {
6580 if (strcmp(t->name, buf) == 0)
6581 break;
6582 }
6583 if (!t) {
6584 ret = -EINVAL;
6585 goto out;
6586 }
6587 if (t == tr->current_trace)
6588 goto out;
6589
6590 #ifdef CONFIG_TRACER_SNAPSHOT
6591 if (t->use_max_tr) {
6592 local_irq_disable();
6593 arch_spin_lock(>max_lock);
6594 if (tr->cond_snapshot)
6595 ret = -EBUSY;
6596 arch_spin_unlock(>max_lock);
6597 local_irq_enable();
6598 if (ret)
6599 goto out;
6600 }
6601 #endif
6602 /* Some tracers won't work on kernel command line */
6603 if (system_state < SYSTEM_RUNNING && t->noboot) {
6604 pr_warn("Tracer '%s' is not allowed on command line,
ignored\n",
6605 t->name);
6606 goto out;
6607 }
6608
6609 /* Some tracers are only allowed for the top level buffer */
6610 if (!trace_ok_for_array(t, tr)) {
6611 ret = -EINVAL;
6612 goto out;
6613 }
6614
6615 /* If trace pipe files are being read, we can't change the
tracer */
6616 if (tr->trace_ref) {
6617 ret = -EBUSY;
6618 goto out;
6619 }
6620
6621 trace_branch_disable();
6622
6623 tr->current_trace->enabled--;
6624
6625 if (tr->current_trace->reset)
6626 tr->current_trace->reset(tr);
6627
6628 #ifdef CONFIG_TRACER_MAX_TRACE
6629 had_max_tr = tr->current_trace->use_max_tr;
6630
6631 /* Current trace needs to be nop_trace before synchronize_rcu */
6632 tr->current_trace = _trace;
6633
6634 if (had_max_tr && !t->use_max_tr) {
6635 /*
6636 * We need to make sure that the update_max_tr sees that
6637 * curren
[linus:master] [tracing] bb32500fb9: BUG:KASAN:slab-use-after-free_in_tracing_open_file_tr
Hello,
kernel test robot noticed
"BUG:KASAN:slab-use-after-free_in_tracing_open_file_tr" on:
commit: bb32500fb9b78215e4ef6ee8b4345c5f5d7eafb4 ("tracing: Have
trace_event_file have ref counters")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master ecb1b8288dc7ccbdcb3b9df005fa1c0e0c0388a7]
[test failed on linux-next/master 01af33cc9894b4489fb68fa35c40e9fe85df63dc]
in testcase: kernel-selftests
version: kernel-selftests-x86_64-60acb023-1_20230329
with following parameters:
group: user_events
compiler: gcc-12
test machine: 36 threads 1 sockets Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz
(Cascade Lake) with 32G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
we noticed this issue is random (6 out of 20 runs as below).
at the same time, we also observed there is an issue
"dmesg.BUG:KASAN:slab-use-after-free_in_event_enable_write"
always happens on parent in all 20 runs.
the parent dmesg is attached FYI.
dcc4e5728eeaeda8 bb32500fb9b78215e4ef6ee8b43
---
fail:runs %reproductionfail:runs
| | |
20:20-100%:20
dmesg.BUG:KASAN:slab-use-after-free_in_event_enable_write
:20 30% 6:20
dmesg.BUG:KASAN:slab-use-after-free_in_tracing_open_file_tr
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-lkp/202401291521.1322c280-oliver.s...@intel.com
[ 108.154115][ T2177] BUG: KASAN: slab-use-after-free in tracing_open_file_tr
(kernel/trace/trace.c:4984)
[ 108.154911][ T2177] Read of size 8 at addr 888273293a50 by task
ftrace_test/2177
[ 108.155680][ T2177]
[ 108.156009][ T2177] CPU: 8 PID: 2177 Comm: ftrace_test Not tainted
6.6.0-rc4-00021-gbb32500fb9b7 #1
[ 108.156886][ T2177] Hardware name: Gigabyte Technology Co., Ltd. X299 UD4
Pro/X299 UD4 Pro-CF, BIOS F8a 04/27/2021
[ 108.157878][ T2177] Call Trace:
[ 108.158275][ T2177]
[ 108.158650][ T2177] dump_stack_lvl (lib/dump_stack.c:108)
[ 108.159135][ T2177] print_address_description+0x2c/0x3a0
[ 108.159775][ T2177] ? tracing_open_file_tr (kernel/trace/trace.c:4984)
[ 108.160351][ T2177] print_report (mm/kasan/report.c:476)
[ 108.160795][ T2177] ? kasan_addr_to_slab (mm/kasan/common.c:35)
[ 108.161279][ T2177] ? tracing_open_file_tr (kernel/trace/trace.c:4984)
[ 108.161798][ T2177] kasan_report (mm/kasan/report.c:590)
[ 108.162246][ T2177] ? tracing_open_file_tr (kernel/trace/trace.c:4984)
[ 108.162768][ T2177] tracing_open_file_tr (kernel/trace/trace.c:4984)
[ 108.163277][ T2177] do_dentry_open (fs/open.c:929)
[ 108.163750][ T2177] ? tracing_is_disabled (kernel/trace/trace.c:4973)
[ 108.164257][ T2177] ? may_open (fs/namei.c:3268)
[ 108.164686][ T2177] do_open (fs/namei.c:3639)
[ 108.165105][ T2177] path_openat (fs/namei.c:3797)
[ 108.165549][ T2177] ? path_lookupat (fs/namei.c:3778)
[ 108.166018][ T2177] ? __lock_acquire (kernel/locking/lockdep.c:5136)
[ 108.166513][ T2177] do_filp_open (fs/namei.c:3823)
[ 108.166974][ T2177] ? may_open_dev (fs/namei.c:3817)
[ 108.167425][ T2177] ? _raw_spin_unlock (arch/x86/include/asm/preempt.h:95
include/linux/spinlock_api_smp.h:143 kernel/locking/spinlock.c:186)
[ 108.167910][ T2177] ? alloc_fd (fs/file.c:555 (discriminator 10))
[ 108.168361][ T2177] do_sys_openat2 (fs/open.c:1422)
[ 108.168838][ T2177] ? build_open_flags (fs/open.c:1408)
[ 108.169333][ T2177] __x64_sys_openat (fs/open.c:1448)
[ 108.169824][ T2177] ? __x64_sys_open (fs/open.c:1448)
[ 108.170304][ T2177] ? lockdep_hardirqs_on_prepare
(kernel/locking/lockdep.c:4565)
[ 108.170935][ T2177] ? syscall_enter_from_user_mode
(arch/x86/include/asm/irqflags.h:42 arch/x86/include/asm/irqflags.h:77
kernel/entry/common.c:111)
[ 108.171545][ T2177] do_syscall_64 (arch/x86/entry/common.c:50
arch/x86/entry/common.c:80)
[ 108.172051][ T2177] entry_SYSCALL_64_after_hwframe
(arch/x86/entry/entry_64.S:120)
[ 108.172672][ T2177] RIP: 0033:0x7f955d2e6e51
[ 108.173166][ T2177] Code: 75 57 89 f0 25 00 00 41 00 3d 00 00 41 00 74 49 80
3d 9a 27 0e 00 00 74 6d 89 da 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48>
3d 00 f0 ff ff 0f 87 93 00 00 00 48 8b 54 24 28 64 48 2b 14 25
All code
0: 75 57 jne0x59
2: 89 f0 mov%esi,%eax
4: 25 00 00 41 00 and$0x41,%eax
9: 3d 00 00 41 00 cmp$0x41,%eax
e: 74 49 je 0x59
10: 80 3d 9a 27 0e 00 00cmpb $0x0,0xe279a(%rip)# 0xe27b1
17: 74 6d je 0x86
19: 89 da mov%ebx,%edx
1b: 48 89 eemov%rbp,%rsi
1e: bf 9c ff ff ff mov$0xff9c,%edi
23: b8 01
[linus:master] [eventfs] 852e46e239: BUG:unable_to_handle_page_fault_for_address
Hello,
kernel test robot noticed "BUG:unable_to_handle_page_fault_for_address" on:
commit: 852e46e239ee6db3cd220614cf8bce96e79227c2 ("eventfs: Do not create
dentries nor inodes in iterate_shared")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 7ed2632ec7d72e926b9e8bcc9ad1bb0cd37274bf]
[test failed on linux-next/master 774551425799cb5bbac94e1768fd69eec4f78dd4]
in testcase: stress-ng
version: stress-ng-x86_64-1744999cb-1_20240112
with following parameters:
nr_threads: 10%
disk: 1HDD
testtime: 60s
fs: xfs
class: filesystem
test: getdent
cpufreq_governor: performance
compiler: gcc-12
test machine: 64 threads 2 sockets Intel(R) Xeon(R) Gold 6346 CPU @ 3.10GHz
(Ice Lake) with 256G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
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-lkp/202401291043.e62e89dc-oliver.s...@intel.com
[ 52.318955][ T4398] BUG: unable to handle page fault for address:
042c04db
[ 52.326780][ T4398] #PF: supervisor read access in kernel mode
[ 52.332830][ T4398] #PF: error_code(0x) - not-present page
[ 52.338864][ T4398] PGD 186970067 P4D 0
[ 52.342993][ T4398] Oops: [#1] SMP NOPTI
[ 52.347552][ T4398] CPU: 32 PID: 4398 Comm: stress-ng-getde Not tainted
6.7.0-rc2-00049-g852e46e239ee #1
[ 52.357235][ T4398] Hardware name: Inspur NF5180M6/NF5180M6, BIOS 06.00.04
04/12/2022
[ 52.365278][ T4398] RIP: 0010:set_top_events_ownership
(fs/tracefs/event_inode.c:172 (discriminator 1))
[ 52.371424][ T4398] Code: 00 00 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90
90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 48 8b 47 f8 48 85 c0 74 11
40 78 02 74 0b 8b 50 50 f7 c2 00 00 08 00 75 05 c3 cc cc cc cc
All code
0: 00 00 add%al,(%rax)
2: 66 2e 0f 1f 84 00 00nopw %cs:0x0(%rax,%rax,1)
9: 00 00 00
c: 90 nop
d: 90 nop
e: 90 nop
f: 90 nop
10: 90 nop
11: 90 nop
12: 90 nop
13: 90 nop
14: 90 nop
15: 90 nop
16: 90 nop
17: 90 nop
18: 90 nop
19: 90 nop
1a: 90 nop
1b: 90 nop
1c: 0f 1f 44 00 00 nopl 0x0(%rax,%rax,1)
21: 48 8b 47 f8 mov-0x8(%rdi),%rax
25: 48 85 c0test %rax,%rax
28: 74 11 je 0x3b
2a:* f6 40 78 02 testb $0x2,0x78(%rax) <-- trapping
instruction
2e: 74 0b je 0x3b
30: 8b 50 50mov0x50(%rax),%edx
33: f7 c2 00 00 08 00 test $0x8,%edx
39: 75 05 jne0x40
3b: c3 retq
3c: cc int3
3d: cc int3
3e: cc int3
3f: cc int3
Code starting with the faulting instruction
===
0: f6 40 78 02 testb $0x2,0x78(%rax)
4: 74 0b je 0x11
6: 8b 50 50mov0x50(%rax),%edx
9: f7 c2 00 00 08 00 test $0x8,%edx
f: 75 05 jne0x16
11: c3 retq
12: cc int3
13: cc int3
14: cc int3
15: cc int3
[ 52.391324][ T4398] RSP: 0018:ffa00f2efc90 EFLAGS: 00010206
[ 52.397481][ T4398] RAX: 042c0463 RBX: ff110002452ae2c8 RCX:
4000
[ 52.405547][ T4398] RDX: 0024 RSI: ff110002452ae2c8 RDI:
ff110002452ae2c8
[ 52.413616][ T4398] RBP: 83080320 R08: 0064 R09:
ff1100018a25dd40
[ 52.421686][ T4398] R10: 8c98 R11: R12:
0024
[ 52.429755][ T4398] R13: 83080320 R14: ffa00f2efedc R15:
00018000
[ 52.437828][ T4398] FS: 7f3b60e3d740() GS:ff11001fffe0()
knlGS:
[ 52.446854][ T4398] CS: 0010 DS: ES: CR0: 80050033
[ 52.453547][ T4398] CR2: 042c04db CR3: 000113750004 CR4:
00771ef0
[ 52.461629][ T4398] DR0: DR1: DR2:
[ 52.469707][ T4398] DR3: DR6: fffe0ff0 DR7:
0400
[ 52.477783][ T4398] PKRU: 5554
[ 52.481444][ T4398] Call Trace:
[ 52.484848][ T4398
Re: [PATCH net-next 2/2] tun: AF_XDP Rx zero-copy support
Hi Yunjian,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url:
https://github.com/intel-lab-lkp/linux/commits/Yunjian-Wang/xsk-Remove-non-zero-dma_page-check-in-xp_assign_dev/20240124-174011
base: net-next/main
patch link:
https://lore.kernel.org/r/1706089075-16084-1-git-send-email-wangyunjian%40huawei.com
patch subject: [PATCH net-next 2/2] tun: AF_XDP Rx zero-copy support
config: i386-randconfig-062-20240127
(https://download.01.org/0day-ci/archive/20240128/202401281735.bx1dign9-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240128/202401281735.bx1dign9-...@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/202401281735.bx1dign9-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/net/tun.c:1298:5: sparse: sparse: symbol 'tun_xsk_pool_setup' was
>> not declared. Should it be static?
drivers/net/tun.c: note: in included file (through include/linux/mmzone.h,
include/linux/gfp.h, include/linux/umh.h, include/linux/kmod.h, ...):
include/linux/page-flags.h:242:46: sparse: sparse: self-comparison always
evaluates to false
vim +/tun_xsk_pool_setup +1298 drivers/net/tun.c
1297
> 1298 int tun_xsk_pool_setup(struct net_device *dev, struct xsk_buff_pool
> *pool,
1299 u16 qid)
1300 {
1301 return pool ? tun_xsk_pool_enable(dev, pool, qid) :
1302 tun_xsk_pool_disable(dev, qid);
1303 }
1304
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH net-next 2/2] tun: AF_XDP Rx zero-copy support
Hi Yunjian,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url:
https://github.com/intel-lab-lkp/linux/commits/Yunjian-Wang/xsk-Remove-non-zero-dma_page-check-in-xp_assign_dev/20240124-174011
base: net-next/main
patch link:
https://lore.kernel.org/r/1706089075-16084-1-git-send-email-wangyunjian%40huawei.com
patch subject: [PATCH net-next 2/2] tun: AF_XDP Rx zero-copy support
config: s390-defconfig
(https://download.01.org/0day-ci/archive/20240128/202401281639.ybajz4sh-...@intel.com/config)
compiler: s390-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240128/202401281639.ybajz4sh-...@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/202401281639.ybajz4sh-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/net/tun.c:1298:5: warning: no previous prototype for
>> 'tun_xsk_pool_setup' [-Wmissing-prototypes]
1298 | int tun_xsk_pool_setup(struct net_device *dev, struct xsk_buff_pool
*pool,
| ^~
vim +/tun_xsk_pool_setup +1298 drivers/net/tun.c
1297
> 1298 int tun_xsk_pool_setup(struct net_device *dev, struct xsk_buff_pool
> *pool,
1299 u16 qid)
1300 {
1301 return pool ? tun_xsk_pool_enable(dev, pool, qid) :
1302 tun_xsk_pool_disable(dev, qid);
1303 }
1304
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH net-next 2/2] tun: AF_XDP Rx zero-copy support
Hi Yunjian, kernel test robot noticed the following build warnings: [auto build test WARNING on net-next/main] url: https://github.com/intel-lab-lkp/linux/commits/Yunjian-Wang/xsk-Remove-non-zero-dma_page-check-in-xp_assign_dev/20240124-174011 base: net-next/main patch link: https://lore.kernel.org/r/1706089075-16084-1-git-send-email-wangyunjian%40huawei.com patch subject: [PATCH net-next 2/2] tun: AF_XDP Rx zero-copy support config: um-allmodconfig (https://download.01.org/0day-ci/archive/20240127/202401271943.bs1gpeeu-...@intel.com/config) compiler: clang version 18.0.0git (https://github.com/llvm/llvm-project a31a60074717fc40887cfe132b77eec93bedd307) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240127/202401271943.bs1gpeeu-...@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/202401271943.bs1gpeeu-...@intel.com/ All warnings (new ones prefixed by >>): In file included from drivers/net/tun.c:44: In file included from include/linux/skbuff.h:17: In file included from include/linux/bvec.h:10: In file included from include/linux/highmem.h:12: In file included from include/linux/hardirq.h:11: In file included from arch/um/include/asm/hardirq.h:5: In file included from include/asm-generic/hardirq.h:17: In file included from include/linux/irq.h:20: In file included from include/linux/io.h:13: In file included from arch/um/include/asm/io.h:24: include/asm-generic/io.h:547:31: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 547 | val = __raw_readb(PCI_IOBASE + addr); | ~~ ^ include/asm-generic/io.h:560:61: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 560 | val = __le16_to_cpu((__le16 __force)__raw_readw(PCI_IOBASE + addr)); | ~~ ^ include/uapi/linux/byteorder/little_endian.h:37:51: note: expanded from macro '__le16_to_cpu' 37 | #define __le16_to_cpu(x) ((__force __u16)(__le16)(x)) | ^ In file included from drivers/net/tun.c:44: In file included from include/linux/skbuff.h:17: In file included from include/linux/bvec.h:10: In file included from include/linux/highmem.h:12: In file included from include/linux/hardirq.h:11: In file included from arch/um/include/asm/hardirq.h:5: In file included from include/asm-generic/hardirq.h:17: In file included from include/linux/irq.h:20: In file included from include/linux/io.h:13: In file included from arch/um/include/asm/io.h:24: include/asm-generic/io.h:573:61: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 573 | val = __le32_to_cpu((__le32 __force)__raw_readl(PCI_IOBASE + addr)); | ~~ ^ include/uapi/linux/byteorder/little_endian.h:35:51: note: expanded from macro '__le32_to_cpu' 35 | #define __le32_to_cpu(x) ((__force __u32)(__le32)(x)) | ^ In file included from drivers/net/tun.c:44: In file included from include/linux/skbuff.h:17: In file included from include/linux/bvec.h:10: In file included from include/linux/highmem.h:12: In file included from include/linux/hardirq.h:11: In file included from arch/um/include/asm/hardirq.h:5: In file included from include/asm-generic/hardirq.h:17: In file included from include/linux/irq.h:20: In file included from include/linux/io.h:13: In file included from arch/um/include/asm/io.h:24: include/asm-generic/io.h:584:33: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 584 | __raw_writeb(value, PCI_IOBASE + addr); | ~~ ^ include/asm-generic/io.h:594:59: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 594 | __raw_writew((u16 __force)cpu_to_le16(value), PCI_IOBASE + addr); | ~~ ^ include/asm-generic/io.h:604:59: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 604 | __raw_writel((u32 __force)cpu_to_le32(value), PCI_IOBASE + addr); | ~~ ^ include/asm-generic/io.h:692:20: warning: performing pointer arithmetic on a null pointer has undefined be
Re: [PATCH v12 3/6] tracing: Add snapshot refcount
Hi Vincent,
kernel test robot noticed the following build errors:
[auto build test ERROR on 4f1991a92cfe89096b2d1f5583a2e093bdd55c37]
url:
https://github.com/intel-lab-lkp/linux/commits/Vincent-Donnefort/ring-buffer-Zero-ring-buffer-sub-buffers/20240123-191131
base: 4f1991a92cfe89096b2d1f5583a2e093bdd55c37
patch link:
https://lore.kernel.org/r/20240123110757.3657908-4-vdonnefort%40google.com
patch subject: [PATCH v12 3/6] tracing: Add snapshot refcount
config: i386-randconfig-012-20240126
(https://download.01.org/0day-ci/archive/20240126/202401261026.cc8ubwxf-...@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240126/202401261026.cc8ubwxf-...@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/202401261026.cc8ubwxf-...@intel.com/
All errors (new ones prefixed by >>):
kernel/trace/trace.c: In function 'tracing_set_tracer':
>> kernel/trace/trace.c:6645:9: error: 'struct tracer' has no member named
>> 'use_max_tr'
6645 |if (t->use_max_tr)
| ^~
>> kernel/trace/trace.c:6646:5: error: implicit declaration of function
>> 'tracing_disarm_snapshot_locked'; did you mean 'tracing_disarm_snapshot'?
>> [-Werror=implicit-function-declaration]
6646 | tracing_disarm_snapshot_locked(tr);
| ^~
| tracing_disarm_snapshot
cc1: some warnings being treated as errors
vim +6645 kernel/trace/trace.c
6641
6642 if (t->init) {
6643 ret = tracer_init(t, tr);
6644 if (ret) {
> 6645 if (t->use_max_tr)
> 6646 tracing_disarm_snapshot_locked(tr);
6647 goto out;
6648 }
6649 }
6650
6651 tr->current_trace = t;
6652 tr->current_trace->enabled++;
6653 trace_branch_enable(tr);
6654 out:
6655 mutex_unlock(_types_lock);
6656
6657 return ret;
6658 }
6659
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v12 3/6] tracing: Add snapshot refcount
Hi Vincent,
kernel test robot noticed the following build errors:
[auto build test ERROR on 4f1991a92cfe89096b2d1f5583a2e093bdd55c37]
url:
https://github.com/intel-lab-lkp/linux/commits/Vincent-Donnefort/ring-buffer-Zero-ring-buffer-sub-buffers/20240123-191131
base: 4f1991a92cfe89096b2d1f5583a2e093bdd55c37
patch link:
https://lore.kernel.org/r/20240123110757.3657908-4-vdonnefort%40google.com
patch subject: [PATCH v12 3/6] tracing: Add snapshot refcount
config: i386-buildonly-randconfig-005-20240126
(https://download.01.org/0day-ci/archive/20240126/202401260918.sn23mdek-...@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project
6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240126/202401260918.sn23mdek-...@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/202401260918.sn23mdek-...@intel.com/
All errors (new ones prefixed by >>):
>> kernel/trace/trace.c:6645:11: error: no member named 'use_max_tr' in 'struct
>> tracer'
6645 | if (t->use_max_tr)
| ~ ^
>> kernel/trace/trace.c:6646:5: error: call to undeclared function
>> 'tracing_disarm_snapshot_locked'; ISO C99 and later do not support implicit
>> function declarations [-Wimplicit-function-declaration]
6646 | tracing_disarm_snapshot_locked(tr);
| ^
kernel/trace/trace.c:6646:5: note: did you mean 'tracing_disarm_snapshot'?
kernel/trace/trace.h:1986:20: note: 'tracing_disarm_snapshot' declared here
1986 | static inline void tracing_disarm_snapshot(struct trace_array *tr) {
}
|^
2 errors generated.
vim +6645 kernel/trace/trace.c
6641
6642 if (t->init) {
6643 ret = tracer_init(t, tr);
6644 if (ret) {
> 6645 if (t->use_max_tr)
> 6646 tracing_disarm_snapshot_locked(tr);
6647 goto out;
6648 }
6649 }
6650
6651 tr->current_trace = t;
6652 tr->current_trace->enabled++;
6653 trace_branch_enable(tr);
6654 out:
6655 mutex_unlock(_types_lock);
6656
6657 return ret;
6658 }
6659
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/3] tracing/probes: support '%pd' type for print struct dentry's name
Hi Ye,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.7 next-20240119]
[cannot apply to rostedt-trace/for-next rostedt-trace/for-next-urgent]
[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/Ye-Bin/tracing-probes-support-pd-type-for-print-struct-dentry-s-name/20240119-093912
base: linus/master
patch link:
https://lore.kernel.org/r/20240119013848.3111364-2-yebin10%40huawei.com
patch subject: [PATCH 1/3] tracing/probes: support '%pd' type for print struct
dentry's name
config: i386-randconfig-051-20240120
(https://download.01.org/0day-ci/archive/20240120/202401201403.atebo79s-...@intel.com/config)
compiler: ClangBuiltLinux clang version 17.0.6
(https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240120/202401201403.atebo79s-...@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/202401201403.atebo79s-...@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/trace/trace_probe.c:1107:8: warning: format specifies type 'unsigned
>> long' but the argument has type 'unsigned int' [-Wformat]
1106 | if (snprintf(new_argv, len, "+0x%lx(%s)",
| ~~~
| %x
1107 | offsetof(struct dentry, d_name.name), argv) >=
len) {
| ^~~~
include/linux/stddef.h:16:32: note: expanded from macro 'offsetof'
16 | #define offsetof(TYPE, MEMBER) __builtin_offsetof(TYPE, MEMBER)
| ^~~~
1 warning generated.
vim +1107 kernel/trace/trace_probe.c
1095
1096 static char* traceprobe_expand_dentry(const char *argv)
1097 {
1098 #define DENTRY_EXPAND_LEN 7 /* +0xXX() */
1099 char *new_argv;
1100 int len = strlen(argv) + 1 + DENTRY_EXPAND_LEN;
1101
1102 new_argv = kmalloc(len, GFP_KERNEL);
1103 if (!new_argv)
1104 return NULL;
1105
1106 if (snprintf(new_argv, len, "+0x%lx(%s)",
> 1107 offsetof(struct dentry, d_name.name), argv) >=
> len) {
1108 kfree(new_argv);
1109 return NULL;
1110 }
1112 return new_argv;
1113 }
1114
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/3] tracing/probes: support '%pd' type for print struct dentry's name
Hi Ye,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.7 next-20240119]
[cannot apply to rostedt-trace/for-next rostedt-trace/for-next-urgent]
[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/Ye-Bin/tracing-probes-support-pd-type-for-print-struct-dentry-s-name/20240119-093912
base: linus/master
patch link:
https://lore.kernel.org/r/20240119013848.3111364-2-yebin10%40huawei.com
patch subject: [PATCH 1/3] tracing/probes: support '%pd' type for print struct
dentry's name
config: i386-defconfig
(https://download.01.org/0day-ci/archive/20240120/202401200837.b9degdbt-...@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240120/202401200837.b9degdbt-...@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/202401200837.b9degdbt-...@intel.com/
All warnings (new ones prefixed by >>):
kernel/trace/trace_probe.c: In function 'traceprobe_expand_dentry':
>> kernel/trace/trace_probe.c:1106:36: warning: format '%lx' expects argument
>> of type 'long unsigned int', but argument 4 has type 'unsigned int'
>> [-Wformat=]
if (snprintf(new_argv, len, "+0x%lx(%s)",
~~^
%x
vim +1106 kernel/trace/trace_probe.c
1095
1096 static char* traceprobe_expand_dentry(const char *argv)
1097 {
1098 #define DENTRY_EXPAND_LEN 7 /* +0xXX() */
1099 char *new_argv;
1100 int len = strlen(argv) + 1 + DENTRY_EXPAND_LEN;
1101
1102 new_argv = kmalloc(len, GFP_KERNEL);
1103 if (!new_argv)
1104 return NULL;
1105
> 1106 if (snprintf(new_argv, len, "+0x%lx(%s)",
1107 offsetof(struct dentry, d_name.name), argv) >=
len) {
1108 kfree(new_argv);
1109 return NULL;
1110 }
1112 return new_argv;
1113 }
1114
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 4/4] remoteproc: stm32: Add support of an OP-TEE TA to load the firmware
Hi Arnaud, kernel test robot noticed the following build errors: [auto build test ERROR on remoteproc/rproc-next] [also build test ERROR on linus/master v6.7 next-20240117] [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/Arnaud-Pouliquen/remoteproc-Add-TEE-support/20240115-215613 base: git://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git rproc-next patch link: https://lore.kernel.org/r/20240115135249.296822-5-arnaud.pouliquen%40foss.st.com patch subject: [PATCH 4/4] remoteproc: stm32: Add support of an OP-TEE TA to load the firmware config: arm64-randconfig-r081-20240118 (https://download.01.org/0day-ci/archive/20240118/202401181522.bvg4emu4-...@intel.com/config) compiler: aarch64-linux-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240118/202401181522.bvg4emu4-...@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/202401181522.bvg4emu4-...@intel.com/ All errors (new ones prefixed by >>): aarch64-linux-ld: drivers/remoteproc/tee_remoteproc.o: in function `tee_rproc_load_fw': >> tee_remoteproc.c:(.text+0x138): undefined reference to >> `tee_shm_register_kernel_buf' >> tee_remoteproc.c:(.text+0x138): relocation truncated to fit: >> R_AARCH64_CALL26 against undefined symbol `tee_shm_register_kernel_buf' >> aarch64-linux-ld: tee_remoteproc.c:(.text+0x18c): undefined reference to >> `tee_client_invoke_func' >> tee_remoteproc.c:(.text+0x18c): relocation truncated to fit: >> R_AARCH64_CALL26 against undefined symbol `tee_client_invoke_func' >> aarch64-linux-ld: tee_remoteproc.c:(.text+0x1ac): undefined reference to >> `tee_shm_free' >> tee_remoteproc.c:(.text+0x1ac): relocation truncated to fit: >> R_AARCH64_CALL26 against undefined symbol `tee_shm_free' aarch64-linux-ld: drivers/remoteproc/tee_remoteproc.o: in function `tee_rproc_start': >> tee_remoteproc.c:(.text+0x240): undefined reference to >> `tee_client_invoke_func' tee_remoteproc.c:(.text+0x240): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `tee_client_invoke_func' aarch64-linux-ld: drivers/remoteproc/tee_remoteproc.o: in function `rproc_tee_get_rsc_table': tee_remoteproc.c:(.text+0x2dc): undefined reference to `tee_client_invoke_func' tee_remoteproc.c:(.text+0x2dc): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `tee_client_invoke_func' aarch64-linux-ld: drivers/remoteproc/tee_remoteproc.o: in function `tee_rproc_stop': tee_remoteproc.c:(.text+0x408): undefined reference to `tee_client_invoke_func' tee_remoteproc.c:(.text+0x408): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `tee_client_invoke_func' aarch64-linux-ld: drivers/remoteproc/tee_remoteproc.o: in function `tee_rproc_register': >> tee_remoteproc.c:(.text+0x51c): undefined reference to >> `tee_client_open_session' >> tee_remoteproc.c:(.text+0x51c): relocation truncated to fit: >> R_AARCH64_CALL26 against undefined symbol `tee_client_open_session' aarch64-linux-ld: drivers/remoteproc/tee_remoteproc.o: in function `tee_rproc_unregister': >> tee_remoteproc.c:(.text+0x624): undefined reference to >> `tee_client_close_session' >> tee_remoteproc.c:(.text+0x624): relocation truncated to fit: >> R_AARCH64_CALL26 against undefined symbol `tee_client_close_session' aarch64-linux-ld: drivers/remoteproc/tee_remoteproc.o: in function `tee_rproc_probe': >> tee_remoteproc.c:(.text+0x6b0): undefined reference to >> `tee_client_open_context' >> tee_remoteproc.c:(.text+0x6b0): relocation truncated to fit: >> R_AARCH64_CALL26 against undefined symbol `tee_client_open_context' >> aarch64-linux-ld: tee_remoteproc.c:(.text+0x6e0): undefined reference to >> `tee_client_close_context' >> tee_remoteproc.c:(.text+0x6e0): relocation truncated to fit: >> R_AARCH64_CALL26 against undefined symbol `tee_client_close_context' aarch64-linux-ld: drivers/remoteproc/tee_remoteproc.o: in function `tee_rproc_remove': tee_remoteproc.c:(.text+0x78c): undefined reference to `tee_client_close_session' tee_remoteproc.c:(.text+0x78c): additional relocation overflows omitted from the output aarch64-linux-ld: tee_remoteproc.c:(.text+0x7dc): undefined reference to `tee_client_close_context' >> aarch64-linux-ld: drivers/remoteproc/tee_remoteproc.o:(.data+0x10): >> undefined reference to `tee_bus_type' Kconfig warnings
Re: [PATCH 4/4] remoteproc: stm32: Add support of an OP-TEE TA to load the firmware
Hi Arnaud,
kernel test robot noticed the following build warnings:
[auto build test WARNING on remoteproc/rproc-next]
[also build test WARNING on robh/for-next linus/master v6.7 next-20240117]
[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/Arnaud-Pouliquen/remoteproc-Add-TEE-support/20240115-215613
base: git://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git
rproc-next
patch link:
https://lore.kernel.org/r/20240115135249.296822-5-arnaud.pouliquen%40foss.st.com
patch subject: [PATCH 4/4] remoteproc: stm32: Add support of an OP-TEE TA to
load the firmware
config: mips-randconfig-r112-20240117
(https://download.01.org/0day-ci/archive/20240118/202401180740.1ud9pjyn-...@intel.com/config)
compiler: clang version 18.0.0git (https://github.com/llvm/llvm-project
9bde5becb44ea071f5e1fa1f5d4071dc8788b18c)
reproduce:
(https://download.01.org/0day-ci/archive/20240118/202401180740.1ud9pjyn-...@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/202401180740.1ud9pjyn-...@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/remoteproc/tee_remoteproc.c:82:26: sparse: sparse: symbol
'tee_rproc_ctx' was not declared. Should it be static?
drivers/remoteproc/tee_remoteproc.c:166:24: sparse: sparse: incorrect type
in assignment (different address spaces) @@ expected void *rsc_va @@
got void [noderef] __iomem * @@
drivers/remoteproc/tee_remoteproc.c:166:24: sparse: expected void *rsc_va
drivers/remoteproc/tee_remoteproc.c:166:24: sparse: got void [noderef]
__iomem *
>> drivers/remoteproc/tee_remoteproc.c:233:31: sparse: sparse: incorrect type
>> in argument 1 (different address spaces) @@ expected void const volatile
>> [noderef] __iomem *addr @@ got void *rsc_va @@
drivers/remoteproc/tee_remoteproc.c:233:31: sparse: expected void const
volatile [noderef] __iomem *addr
drivers/remoteproc/tee_remoteproc.c:233:31: sparse: got void *rsc_va
drivers/remoteproc/tee_remoteproc.c: note: in included file (through
include/linux/preempt.h, include/linux/spinlock.h, include/linux/mmzone.h, ...):
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates
to true
vim +233 drivers/remoteproc/tee_remoteproc.c
6805d1065198e1 Arnaud Pouliquen 2024-01-15 215
6805d1065198e1 Arnaud Pouliquen 2024-01-15 216 int tee_rproc_stop(struct
tee_rproc *trproc)
6805d1065198e1 Arnaud Pouliquen 2024-01-15 217 {
6805d1065198e1 Arnaud Pouliquen 2024-01-15 218 struct
tee_ioctl_invoke_arg arg;
6805d1065198e1 Arnaud Pouliquen 2024-01-15 219 struct tee_param
param[MAX_TEE_PARAM_ARRY_MEMBER];
6805d1065198e1 Arnaud Pouliquen 2024-01-15 220 int ret;
6805d1065198e1 Arnaud Pouliquen 2024-01-15 221
6805d1065198e1 Arnaud Pouliquen 2024-01-15 222 prepare_args(trproc,
TA_RPROC_FW_CMD_STOP_FW, , param, 0);
6805d1065198e1 Arnaud Pouliquen 2024-01-15 223
6805d1065198e1 Arnaud Pouliquen 2024-01-15 224 ret =
tee_client_invoke_func(tee_rproc_ctx->tee_ctx, , param);
6805d1065198e1 Arnaud Pouliquen 2024-01-15 225 if (ret < 0 || arg.ret
!= 0) {
6805d1065198e1 Arnaud Pouliquen 2024-01-15 226
dev_err(tee_rproc_ctx->dev,
6805d1065198e1 Arnaud Pouliquen 2024-01-15 227
"TA_RPROC_FW_CMD_STOP_FW invoke failed TEE err: %x, ret:%x\n",
6805d1065198e1 Arnaud Pouliquen 2024-01-15 228
arg.ret, ret);
6805d1065198e1 Arnaud Pouliquen 2024-01-15 229 if (!ret)
6805d1065198e1 Arnaud Pouliquen 2024-01-15 230 ret =
-EIO;
6805d1065198e1 Arnaud Pouliquen 2024-01-15 231 }
6805d1065198e1 Arnaud Pouliquen 2024-01-15 232 if (trproc->rsc_va)
6805d1065198e1 Arnaud Pouliquen 2024-01-15 @233
iounmap(trproc->rsc_va);
6805d1065198e1 Arnaud Pouliquen 2024-01-15 234 trproc->rsc_va = NULL;
6805d1065198e1 Arnaud Pouliquen 2024-01-15 235
6805d1065198e1 Arnaud Pouliquen 2024-01-15 236 return ret;
6805d1065198e1 Arnaud Pouliquen 2024-01-15 237 }
6805d1065198e1 Arnaud Pouliquen 2024-01-15 238
EXPORT_SYMBOL_GPL(tee_rproc_stop);
6805d1065198e1 Arnaud Pouliquen 2024-01-15 239
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[mhiramat:topic/fprobe-on-fgraph] [function_graph] f2ed0fd5cc: WARNING:at_kernel/trace/trace.c:#run_tracer_selftest
Hello,
kernel test robot noticed
"WARNING:at_kernel/trace/trace.c:#run_tracer_selftest" on:
commit: f2ed0fd5cc77ca2ad957569c35e76ef08cf93f54 ("function_graph: Add a new
entry handler with parent_ip and ftrace_regs")
https://git.kernel.org/cgit/linux/kernel/git/mhiramat/linux.git
topic/fprobe-on-fgraph
in testcase: boot
compiler: gcc-12
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+--+++
| | 2d3653c71e |
f2ed0fd5cc |
+--+++
| WARNING:at_kernel/trace/trace.c:#run_tracer_selftest | 0 | 20
|
| EIP:run_tracer_selftest | 0 | 20
|
+--+++
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-lkp/202401172200.c8731564-oliver.s...@intel.com
[5.535374][T1] Testing tracer function_graph: .. no entries found
..FAILED!
[6.645598][T1] [ cut here ]
[6.646006][T1] WARNING: CPU: 0 PID: 1 at kernel/trace/trace.c:2045
run_tracer_selftest+0x256/0x26c
[6.646759][T1] Modules linked in:
[6.647062][T1] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G
T 6.7.0-rc8-00022-gf2ed0fd5cc77 #1
[6.647669][T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[6.648455][T1] EIP: run_tracer_selftest+0x256/0x26c
[6.648871][T1] Code: 00 00 66 90 8b 15 ec 97 d3 d4 b9 ff ff ff ff a1 28
98 d3 d4 e8 37 68 ff ff e9 26 fe ff ff c7 04 24 90 d6 8c d4 e8 92 68 f6 ff <0f>
0b b8 ff ff ff ff e9 a7 fe ff ff b8 f4 ff ff ff e9 9d fe ff ff
[6.650343][T1] EAX: 0007 EBX: d4e33700 ECX: EDX:
[6.650884][T1] ESI: d4e4a8c0 EDI: c101f100 EBP: c138de8c ESP: c138de78
[6.651422][T1] DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 EFLAGS:
00010246
[6.651661][T1] CR0: 80050033 CR2: ffcb2000 CR3: 14f88000 CR4: 00040690
[6.652189][T1] DR0: DR1: DR2: DR3:
[6.652715][T1] DR6: fffe0ff0 DR7: 0400
[6.653063][T1] Call Trace:
[6.653309][T1] ? show_regs+0x82/0x90
[6.653630][T1] ? run_tracer_selftest+0x256/0x26c
[6.654025][T1] ? __warn+0x89/0x1bc
[6.654333][T1] ? run_tracer_selftest+0x256/0x26c
[6.654733][T1] ? run_tracer_selftest+0x256/0x26c
[6.655128][T1] ? report_bug+0x1c5/0x23c
[6.655467][T1] ? exc_overflow+0x58/0x58
[6.655661][T1] ? handle_bug+0x28/0x50
[6.655984][T1] ? exc_invalid_op+0x28/0x7c
[6.656332][T1] ? preempt_count_sub+0xc9/0x120
[6.656706][T1] ? preempt_count_add+0x69/0xc8
[6.657074][T1] ? vprintk_emit+0x7a/0x194
[6.657418][T1] ? handle_exception+0x14d/0x14d
[6.657794][T1] ? exc_overflow+0x58/0x58
[6.658130][T1] ? run_tracer_selftest+0x256/0x26c
[6.658530][T1] ? exc_overflow+0x58/0x58
[6.658865][T1] ? run_tracer_selftest+0x256/0x26c
[6.659262][T1] register_tracer+0xe4/0x28c
[6.659612][T1] ? register_trace_event+0xf6/0x180
[6.659661][T1] ? init_graph_tracefs+0x3c/0x3c
[6.660036][T1] init_graph_trace+0x56/0x7c
[6.660386][T1] do_one_initcall+0x70/0x3b8
[6.660732][T1] ? parameq+0x13/0x68
[6.661039][T1] ? parse_args+0x202/0x37c
[6.661383][T1] do_initcalls+0x100/0x228
[6.661721][T1] ? rdinit_setup+0x40/0x40
[6.662061][T1] ? rest_init+0x194/0x194
[6.662393][T1] kernel_init_freeable+0xd3/0x1c4
[6.662772][T1] kernel_init+0x1a/0x1dc
[6.663096][T1] ? schedule_tail+0x60/0x78
[6.663439][T1] ret_from_fork+0x3d/0x48
[6.663661][T1] ? rest_init+0x194/0x194
[6.663992][T1] ret_from_fork_asm+0x12/0x18
[6.664348][T1] entry_INT80_32+0x10d/0x10d
[6.664702][T1] irq event stamp: 2172679
[6.665030][T1] hardirqs last enabled at (2172687): []
console_unlock+0x11a/0x178
[6.665694][T1] hardirqs last disabled at (2172694): []
console_unlock+0x101/0x178
[6.666360][T1] softirqs last enabled at (2172316): []
__do_softirq+0x2f3/0x4b4
[6.667009][T1] softirqs last disabled at (2172309): []
do_softirq_own_stack+0x37/0x4c
[6.667661][T1] ---[ end trace ]---
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240117/202401172200.c8731564-oliver.s...@intel.com
--
0-DAY CI Kernel Test Service
https://
[mhiramat:topic/fprobe-on-fgraph] [function_graph] 367c724761: BUG:KASAN:slab-out-of-bounds_in_ftrace_push_return_trace
Hello,
kernel test robot noticed
"BUG:KASAN:slab-out-of-bounds_in_ftrace_push_return_trace" on:
commit: 367c724761b0a49e115dd3bb27e93b3905cfe05a ("function_graph: Improve push
operation for several interrupts")
https://git.kernel.org/cgit/linux/kernel/git/mhiramat/linux.git
topic/fprobe-on-fgraph
in testcase: ftrace-onoff
version:
with following parameters:
runtime: 5m
compiler: gcc-12
test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (Kaby
Lake) with 32G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
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-lkp/202401172217.36e37075-oliver.s...@intel.com
[ 43.381281][ T644] BUG: KASAN: slab-out-of-bounds in
ftrace_push_return_trace+0x7e0/0x820
[ 43.390620][ T644] Write of size 8 at addr 888116ea1ff8 by task cat/644
[ 43.397694][ T644]
[ 43.399903][ T644] CPU: 1 PID: 644 Comm: cat Not tainted
6.7.0-rc8-00020-g367c724761b0 #1
[ 43.408197][ T644] Hardware name: Dell Inc. OptiPlex 7050/062KRH, BIOS
1.2.0 12/22/2016
[ 43.416323][ T644] Call Trace:
[ 43.419491][ T644]
[ 43.422316][ T644] dump_stack_lvl (lib/dump_stack.c:107 (discriminator 1))
[ 43.426715][ T644] print_address_description+0x2c/0x3a0
[ 43.433196][ T644] ? ftrace_push_return_trace+0x7e0/0x820
[ 43.439857][ T644] print_report (mm/kasan/report.c:476)
[ 43.444161][ T644] ? fixup_red_left (mm/slub.c:224)
[ 43.448650][ T644] ? kasan_addr_to_slab (mm/kasan/common.c:35)
[ 43.453485][ T644] ? ftrace_push_return_trace+0x7e0/0x820
[ 43.460143][ T644] kasan_report (mm/kasan/report.c:590)
[ 43.464461][ T644] ? ftrace_push_return_trace+0x7e0/0x820
[ 43.471130][ T644] ? unwind_next_frame (arch/x86/kernel/unwind_orc.c:469)
[ 43.476040][ T644] ? arch_stack_walk (arch/x86/kernel/stacktrace.c:24)
[ 43.480689][ T644] ftrace_push_return_trace+0x7e0/0x820
[ 43.487161][ T644] ? trace_graph_entry (arch/x86/include/asm/atomic.h:60
include/linux/atomic/atomic-arch-fallback.h:1210
include/linux/atomic/atomic-instrumented.h:593
kernel/trace/trace_functions_graph.c:188)
[ 43.492173][ T644] ? unwind_next_frame (arch/x86/kernel/unwind_orc.c:469)
[ 43.497079][ T644] ? arch_stack_walk (arch/x86/kernel/stacktrace.c:24)
[ 43.501724][ T644] function_graph_enter_ops (kernel/trace/fgraph.c:702)
[ 43.507071][ T644] ? kernel_text_address (kernel/extable.c:95)
[ 43.512071][ T644] ? function_graph_enter (kernel/trace/fgraph.c:690)
[ 43.517338][ T644] ? ftrace_graph_func (arch/x86/kernel/ftrace.c:674)
[ 43.522352][ T644] ? kernel_text_address (kernel/extable.c:95)
[ 43.527372][ T644] ? unwind_next_frame (arch/x86/kernel/unwind_orc.c:469)
[ 43.532287][ T644] ftrace_graph_func (arch/x86/kernel/ftrace.c:674)
[ 43.537116][ T644] ? write_profile (kernel/stacktrace.c:83)
[ 43.541769][ T644] 0xc0478087
[ 43.545670][ T644] ? do_exit (kernel/exit.c:859)
[ 43.549799][ T644] ? unwind_next_frame (arch/x86/kernel/unwind_orc.c:471)
[ 43.554715][ T644] unwind_next_frame (arch/x86/kernel/unwind_orc.c:471)
[ 43.559444][ T644] arch_stack_walk (arch/x86/kernel/stacktrace.c:24)
[ 43.563944][ T644] ? do_exit (kernel/exit.c:859)
[ 43.568090][ T644] stack_trace_save (kernel/stacktrace.c:123)
[ 43.572653][ T644] ? filter_irq_stacks (kernel/stacktrace.c:114)
[ 43.577492][ T644] ? stack_trace_save (kernel/stacktrace.c:114)
[ 43.582148][ T644] kasan_save_stack (mm/kasan/common.c:46)
[ 43.586707][ T644] ? kasan_save_stack (mm/kasan/common.c:46)
[ 43.591436][ T644] ? kasan_set_track (mm/kasan/common.c:52)
[ 43.596081][ T644] ? kasan_save_free_info (mm/kasan/generic.c:524)
[ 43.601159][ T644] ? __kasan_slab_free (mm/kasan/common.c:238
mm/kasan/common.c:200 mm/kasan/common.c:244)
[ 43.606150][ T644] ? kmem_cache_free_bulk (mm/slub.c:4037)
[ 43.612010][ T644] ? mt_destroy_walk+0x56f/0xfd0
[ 43.617435][ T644] ? __mt_destroy (lib/maple_tree.c:5338)
[ 43.621906][ T644] ? exit_mmap (arch/x86/include/asm/jump_label.h:27
include/linux/jump_label.h:207 include/linux/mmap_lock.h:41
include/linux/mmap_lock.h:131 mm/mmap.c:3341)
[ 43.626203][ T644] ? __mmput (kernel/fork.c:1350)
[ 43.630241][ T644] ? exit_mm (kernel/exit.c:568)
[ 43.634374][ T644] ? do_exit (kernel/exit.c:859)
[ 43.638643][ T644] ? mt_destroy_walk+0x56f/0xfd0
[ 43.644071][ T644] kasan_set_track (mm/kasan/common.c:52)
[ 43.648544][ T644] kasan_save_free_info (mm/kasan/generic.c:524)
[ 43.653452][ T644] __kasan_slab_free (mm/kasan/common.c:238
mm/kasan/common.c:200 mm/kasan/common.c:244)
[ 43.658280][ T644] kmem_cache_free_bulk (mm/slub.c:4037)
[ 43.663969][ T644] ? mt_destroy_walk+0x56f/0xfd0
[ 43.669445][ T644] mt_destroy_walk+0x56f/0xfd0
[ 43.674747][ T644] __mt_destroy (lib/maple_tree.c:5338)
[ 43.679062][ T644] exit_mmap (arch/x86/include/asm/jump_label.h:27
include/linux/jump
Re: [PATCH 4/4] remoteproc: stm32: Add support of an OP-TEE TA to load the firmware
Hi Arnaud,
kernel test robot noticed the following build warnings:
[auto build test WARNING on remoteproc/rproc-next]
[also build test WARNING on robh/for-next linus/master v6.7 next-20240112]
[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/Arnaud-Pouliquen/remoteproc-Add-TEE-support/20240115-215613
base: git://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git
rproc-next
patch link:
https://lore.kernel.org/r/20240115135249.296822-5-arnaud.pouliquen%40foss.st.com
patch subject: [PATCH 4/4] remoteproc: stm32: Add support of an OP-TEE TA to
load the firmware
config: arm64-allyesconfig
(https://download.01.org/0day-ci/archive/20240116/202401161603.5dlosqij-...@intel.com/config)
compiler: clang version 18.0.0git (https://github.com/llvm/llvm-project
9bde5becb44ea071f5e1fa1f5d4071dc8788b18c)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240116/202401161603.5dlosqij-...@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/202401161603.5dlosqij-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/remoteproc/stm32_rproc.c:977:6: warning: variable 'trproc' is used
>> uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]
977 | if (of_device_is_compatible(np, "st,stm32mp1-m4-tee")) {
| ^
drivers/remoteproc/stm32_rproc.c:991:8: note: uninitialized use occurs here
991 | trproc ? _rproc_tee_ops :
_rproc_ops,
| ^~
drivers/remoteproc/stm32_rproc.c:977:2: note: remove the 'if' if its
condition is always true
977 | if (of_device_is_compatible(np, "st,stm32mp1-m4-tee")) {
| ^~
drivers/remoteproc/stm32_rproc.c:968:26: note: initialize the variable
'trproc' to silence this warning
968 | struct tee_rproc *trproc;
| ^
| = NULL
1 warning generated.
vim +977 drivers/remoteproc/stm32_rproc.c
962
963 static int stm32_rproc_probe(struct platform_device *pdev)
964 {
965 struct device *dev = >dev;
966 struct stm32_rproc *ddata;
967 struct device_node *np = dev->of_node;
968 struct tee_rproc *trproc;
969 struct rproc *rproc;
970 unsigned int state;
971 int ret;
972
973 ret = dma_coerce_mask_and_coherent(dev, DMA_BIT_MASK(32));
974 if (ret)
975 return ret;
976
> 977 if (of_device_is_compatible(np, "st,stm32mp1-m4-tee")) {
978 trproc = tee_rproc_register(dev, STM32_MP1_M4_PROC_ID);
979 if (IS_ERR(trproc)) {
980 dev_err_probe(dev, PTR_ERR(trproc),
981"signed firmware not supported by
TEE\n");
982 return PTR_ERR(trproc);
983 }
984 /*
985 * Delegate the firmware management to the secure
context.
986 * The firmware loaded has to be signed.
987 */
988 dev_info(dev, "Support of signed firmware only\n");
989 }
990 rproc = rproc_alloc(dev, np->name,
991 trproc ? _rproc_tee_ops : _rproc_ops,
992 NULL, sizeof(*ddata));
993 if (!rproc) {
994 ret = -ENOMEM;
995 goto free_tee;
996 }
997
998 ddata = rproc->priv;
999 ddata->trproc = trproc;
1000 if (trproc)
1001 trproc->rproc = rproc;
1002
1003 rproc_coredump_set_elf_info(rproc, ELFCLASS32, EM_NONE);
1004
1005 ret = stm32_rproc_parse_dt(pdev, ddata, >auto_boot);
1006 if (ret)
1007 goto free_rproc;
1008
1009 ret = stm32_rproc_of_memory_translations(pdev, ddata);
1010 if (ret)
1011 goto free_rproc;
1012
1013 ret = stm32_rproc_get_m4_status(ddata, );
1014 if (ret)
1015 goto free_rproc;
1016
1017 if (state == M4_STATE_CRUN)
1018 rproc->state = RPROC_DETACHED;
1019
1020
Re: [PATCH 4/4] remoteproc: stm32: Add support of an OP-TEE TA to load the firmware
Hi Arnaud,
kernel test robot noticed the following build warnings:
[auto build test WARNING on remoteproc/rproc-next]
[also build test WARNING on robh/for-next linus/master v6.7 next-20240112]
[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/Arnaud-Pouliquen/remoteproc-Add-TEE-support/20240115-215613
base: git://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git
rproc-next
patch link:
https://lore.kernel.org/r/20240115135249.296822-5-arnaud.pouliquen%40foss.st.com
patch subject: [PATCH 4/4] remoteproc: stm32: Add support of an OP-TEE TA to
load the firmware
config: um-randconfig-r113-20240116
(https://download.01.org/0day-ci/archive/20240116/202401161552.jwqxl1kd-...@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240116/202401161552.jwqxl1kd-...@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/202401161552.jwqxl1kd-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/remoteproc/tee_remoteproc.c:82:26: sparse: sparse: symbol
>> 'tee_rproc_ctx' was not declared. Should it be static?
>> drivers/remoteproc/tee_remoteproc.c:166:24: sparse: sparse: incorrect type
>> in assignment (different address spaces) @@ expected void *rsc_va @@
>> got void [noderef] __iomem * @@
drivers/remoteproc/tee_remoteproc.c:166:24: sparse: expected void *rsc_va
drivers/remoteproc/tee_remoteproc.c:166:24: sparse: got void [noderef]
__iomem *
>> drivers/remoteproc/tee_remoteproc.c:233:31: sparse: sparse: incorrect type
>> in argument 1 (different address spaces) @@ expected void volatile
>> [noderef] __iomem *addr @@ got void *rsc_va @@
drivers/remoteproc/tee_remoteproc.c:233:31: sparse: expected void
volatile [noderef] __iomem *addr
drivers/remoteproc/tee_remoteproc.c:233:31: sparse: got void *rsc_va
drivers/remoteproc/tee_remoteproc.c: note: in included file (through
include/linux/preempt.h, include/linux/spinlock.h, include/linux/mmzone.h, ...):
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates
to true
vim +/tee_rproc_ctx +82 drivers/remoteproc/tee_remoteproc.c
6805d1065198e1 Arnaud Pouliquen 2024-01-15 81
6805d1065198e1 Arnaud Pouliquen 2024-01-15 @82 struct tee_rproc_context
*tee_rproc_ctx;
6805d1065198e1 Arnaud Pouliquen 2024-01-15 83
6805d1065198e1 Arnaud Pouliquen 2024-01-15 84 static void
prepare_args(struct tee_rproc *trproc, int cmd, struct tee_ioctl_invoke_arg
*arg,
6805d1065198e1 Arnaud Pouliquen 2024-01-15 85 struct
tee_param *param, unsigned int num_params)
6805d1065198e1 Arnaud Pouliquen 2024-01-15 86 {
6805d1065198e1 Arnaud Pouliquen 2024-01-15 87 memset(arg, 0,
sizeof(*arg));
6805d1065198e1 Arnaud Pouliquen 2024-01-15 88 memset(param, 0,
MAX_TEE_PARAM_ARRY_MEMBER * sizeof(*param));
6805d1065198e1 Arnaud Pouliquen 2024-01-15 89
6805d1065198e1 Arnaud Pouliquen 2024-01-15 90 arg->func = cmd;
6805d1065198e1 Arnaud Pouliquen 2024-01-15 91 arg->session =
trproc->session_id;
6805d1065198e1 Arnaud Pouliquen 2024-01-15 92 arg->num_params =
num_params + 1;
6805d1065198e1 Arnaud Pouliquen 2024-01-15 93
6805d1065198e1 Arnaud Pouliquen 2024-01-15 94 param[0] = (struct
tee_param) {
6805d1065198e1 Arnaud Pouliquen 2024-01-15 95 .attr =
TEE_IOCTL_PARAM_ATTR_TYPE_VALUE_INPUT,
6805d1065198e1 Arnaud Pouliquen 2024-01-15 96 .u.value.a =
trproc->rproc_id,
6805d1065198e1 Arnaud Pouliquen 2024-01-15 97 };
6805d1065198e1 Arnaud Pouliquen 2024-01-15 98 }
6805d1065198e1 Arnaud Pouliquen 2024-01-15 99
6805d1065198e1 Arnaud Pouliquen 2024-01-15 100 int tee_rproc_load_fw(struct
tee_rproc *trproc, const struct firmware *fw)
6805d1065198e1 Arnaud Pouliquen 2024-01-15 101 {
6805d1065198e1 Arnaud Pouliquen 2024-01-15 102 struct
tee_ioctl_invoke_arg arg;
6805d1065198e1 Arnaud Pouliquen 2024-01-15 103 struct tee_param
param[MAX_TEE_PARAM_ARRY_MEMBER];
6805d1065198e1 Arnaud Pouliquen 2024-01-15 104 struct tee_shm *fw_shm;
6805d1065198e1 Arnaud Pouliquen 2024-01-15 105 int ret;
6805d1065198e1 Arnaud Pouliquen 2024-01-15 106
6805d1065198e1 Arnaud Pouliquen 2024-01-15 107 fw_shm =
tee_shm_register_kernel_buf(tee_rproc_ctx->tee_ctx, (void *)fw->data, fw->size);
6805d1065198e1 Arnaud Pouliquen 2024-01-15 108 if (IS_ERR(fw_shm))
6
Re: [PATCH 4/4] remoteproc: stm32: Add support of an OP-TEE TA to load the firmware
Hi Arnaud, kernel test robot noticed the following build warnings: [auto build test WARNING on remoteproc/rproc-next] [also build test WARNING on robh/for-next linus/master v6.7 next-20240112] [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/Arnaud-Pouliquen/remoteproc-Add-TEE-support/20240115-215613 base: git://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git rproc-next patch link: https://lore.kernel.org/r/20240115135249.296822-5-arnaud.pouliquen%40foss.st.com patch subject: [PATCH 4/4] remoteproc: stm32: Add support of an OP-TEE TA to load the firmware config: alpha-kismet-CONFIG_TEE_REMOTEPROC-CONFIG_STM32_RPROC-0-0 (https://download.01.org/0day-ci/archive/20240116/202401161447.0aqqneio-...@intel.com/config) reproduce: (https://download.01.org/0day-ci/archive/20240116/202401161447.0aqqneio-...@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/202401161447.0aqqneio-...@intel.com/ kismet warnings: (new ones prefixed by >>) >> kismet: WARNING: unmet direct dependencies detected for TEE_REMOTEPROC when >> selected by STM32_RPROC WARNING: unmet direct dependencies detected for TEE_REMOTEPROC Depends on [n]: REMOTEPROC [=y] && OPTEE [=n] Selected by [y]: - STM32_RPROC [=y] && (ARCH_STM32 || COMPILE_TEST [=y]) && REMOTEPROC [=y] -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
[linux-next:master] [eventfs] 493ec81a8f: kernel_BUG_at_fs/dcache.c
Hello,
kernel test robot noticed "kernel_BUG_at_fs/dcache.c" on:
commit: 493ec81a8fb8e4ada6f223b8b73791a1280d4774 ("eventfs: Stop using
dcache_readdir() for getdents()")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 8cb47d7cd090a690c1785385b2f3d407d4a53ad0]
[test failed on fix commit 1e4624eb5a0ecaae0d2c4e3019bece119725bb98]
in testcase: stress-ng
version: stress-ng-x86_64-3040a078a-1_20231212
with following parameters:
nr_threads: 10%
disk: 1HDD
testtime: 60s
fs: btrfs
class: filesystem
test: getdent
cpufreq_governor: performance
compiler: gcc-12
test machine: 64 threads 2 sockets Intel(R) Xeon(R) Gold 6346 CPU @ 3.10GHz
(Ice Lake) with 256G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
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-lkp/202401152142.bfc28861-oliver.s...@intel.com
[ 41.602502][ T4375] [ cut here ]
[ 41.602519][ T4376] [ cut here ]
[ 41.602607][ T4374] [ cut here ]
[ 41.602607][ T4378] [ cut here ]
[ 41.602608][ T4374] kernel BUG at fs/dcache.c:2031!
[ 41.602608][ T4378] kernel BUG at fs/dcache.c:2031!
[ 41.602613][ T4374] invalid opcode: [#1] SMP NOPTI
[ 41.602616][ T4374] CPU: 50 PID: 4374 Comm: stress-ng-getde Not tainted
6.7.0-rc2-00042-g493ec81a8fb8 #1
[ 41.602618][ T4374] Hardware name: Inspur NF5180M6/NF5180M6, BIOS 06.00.04
04/12/2022
[ 41.602619][ T4374] RIP: 0010:d_instantiate (fs/dcache.c:2031 (discriminator
1))
[ 41.602623][ T4377] [ cut here ]
[ 41.602623][ T4374] Code: e8 92 c0 1c 00 4c 89 e7 e8 0a 79 b8 00 48 89 ef 48
89 de e8 7f fc ff ff 4c 89 e7 c6 07 00 0f 1f 00 5b 5d 41 5c c3 cc cc cc cc <0f>
0b 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 2e 0f 1f 84 00 00 00
All code
0: e8 92 c0 1c 00 callq 0x1cc097
5: 4c 89 e7mov%r12,%rdi
8: e8 0a 79 b8 00 callq 0xb87917
d: 48 89 efmov%rbp,%rdi
10: 48 89 demov%rbx,%rsi
13: e8 7f fc ff ff callq 0xfc97
18: 4c 89 e7mov%r12,%rdi
1b: c6 07 00movb $0x0,(%rdi)
1e: 0f 1f 00nopl (%rax)
21: 5b pop%rbx
22: 5d pop%rbp
23: 41 5c pop%r12
25: c3 retq
26: cc int3
27: cc int3
28: cc int3
29: cc int3
2a:* 0f 0b ud2 <-- trapping instruction
2c: 66 66 2e 0f 1f 84 00data16 nopw %cs:0x0(%rax,%rax,1)
33: 00 00 00 00
37: 66 data16
38: 66 data16
39: 2e cs
3a: 0f .byte 0xf
3b: 1f (bad)
3c: 84 00 test %al,(%rax)
...
Code starting with the faulting instruction
===
0: 0f 0b ud2
2: 66 66 2e 0f 1f 84 00data16 nopw %cs:0x0(%rax,%rax,1)
9: 00 00 00 00
d: 66 data16
e: 66 data16
f: 2e cs
10: 0f .byte 0xf
11: 1f (bad)
12: 84 00 test %al,(%rax)
...
[ 41.602625][ T4377] kernel BUG at fs/dcache.c:2031!
[ 41.602625][ T4374] RSP: 0018:ffa00fcdfcd0 EFLAGS: 00010286
[ 41.602629][ T4374] RAX: 0002 RBX: ff11000109392980 RCX:
[ 41.602630][ T4374] RDX: RSI: ff1100405e46c6f0 RDI:
ff1100405f05afc0
[ 41.602631][ T4374] RBP: ff1100405f05afc0 R08: 830ad0e0 R09:
[ 41.602632][ T4374] R10: 0280 R11: 8162036a R12:
[ 41.602633][ T4374] R13: ff1100405e46c6f0 R14: ff1100405f05aff8 R15:
[ 41.602634][ T4374] FS: 7f2582ff9740() GS:ff1100407fa8()
knlGS:
[ 41.602635][ T4374] CS: 0010 DS: ES: CR0: 80050033
[ 41.602635][ T4374] CR2: 5624511f3328 CR3: 00208a342006 CR4:
00771ef0
[ 41.602636][ T4374] DR0: DR1: DR2:
[ 41.602637][ T4374] DR3: DR6: fffe0ff0 DR7:
0400
[ 41.602638][ T4374] PKRU: 5554
[ 41.602638][ T4374] Call Trace:
[ 41.602640][ T4374]
[ 41.602642][ T4374] ? die (arch/x86/kernel/dumpstack.c:421
arch/x86/kernel/du
Re: [PATCH] mm: Update mark_victim tracepoints fields
Hi Carlos,
kernel test robot noticed the following build errors:
[auto build test ERROR on 0dd3ee31125508cd67f7e7172247f05b7fd1753a]
url:
https://github.com/intel-lab-lkp/linux/commits/Carlos-Galo/mm-Update-mark_victim-tracepoints-fields/20240111-081635
base: 0dd3ee31125508cd67f7e7172247f05b7fd1753a
patch link:
https://lore.kernel.org/r/20240111001155.746-1-carlosgalo%40google.com
patch subject: [PATCH] mm: Update mark_victim tracepoints fields
config: x86_64-defconfig
(https://download.01.org/0day-ci/archive/20240112/202401120052.rdfjpivg-...@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240112/202401120052.rdfjpivg-...@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/202401120052.rdfjpivg-...@intel.com/
All errors (new ones prefixed by >>):
In file included from include/trace/define_trace.h:102,
from include/trace/events/oom.h:206,
from mm/oom_kill.c:54:
include/trace/events/oom.h: In function 'trace_raw_output_mark_victim':
>> include/trace/stages/stage3_trace_output.h:6:17: error: called object is not
>> a function or function pointer
6 | #define __entry field
| ^
include/trace/trace_events.h:203:34: note: in definition of macro
'DECLARE_EVENT_CLASS'
203 | trace_event_printf(iter, print);
\
| ^
include/trace/trace_events.h:45:30: note: in expansion of macro 'PARAMS'
45 | PARAMS(print)); \
| ^~
include/trace/events/oom.h:74:1: note: in expansion of macro 'TRACE_EVENT'
74 | TRACE_EVENT(mark_victim,
| ^~~
include/trace/events/oom.h:93:9: note: in expansion of macro 'TP_printk'
93 | TP_printk("pid=%d uid=%u comm=%s oom_score_adj=%hd",
| ^
include/trace/events/oom.h:95:17: note: in expansion of macro '__entry'
95 | __entry->uid
| ^~~
>> include/trace/trace_events.h:203:39: error: expected expression before ')'
>> token
203 | trace_event_printf(iter, print);
\
| ^
include/trace/trace_events.h:40:9: note: in expansion of macro
'DECLARE_EVENT_CLASS'
40 | DECLARE_EVENT_CLASS(name, \
| ^~~
include/trace/events/oom.h:74:1: note: in expansion of macro 'TRACE_EVENT'
74 | TRACE_EVENT(mark_victim,
| ^~~
vim +6 include/trace/stages/stage3_trace_output.h
af6b9668e85ffd include/trace/stages/stage3_defines.h Steven Rostedt (Google
2022-03-03 4)
af6b9668e85ffd include/trace/stages/stage3_defines.h Steven Rostedt (Google
2022-03-03 5) #undef __entry
af6b9668e85ffd include/trace/stages/stage3_defines.h Steven Rostedt (Google
2022-03-03 @6) #define __entry field
af6b9668e85ffd include/trace/stages/stage3_defines.h Steven Rostedt (Google
2022-03-03 7)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH] mm: Update mark_victim tracepoints fields
Hi Carlos,
kernel test robot noticed the following build errors:
[auto build test ERROR on 0dd3ee31125508cd67f7e7172247f05b7fd1753a]
url:
https://github.com/intel-lab-lkp/linux/commits/Carlos-Galo/mm-Update-mark_victim-tracepoints-fields/20240111-081635
base: 0dd3ee31125508cd67f7e7172247f05b7fd1753a
patch link:
https://lore.kernel.org/r/20240111001155.746-1-carlosgalo%40google.com
patch subject: [PATCH] mm: Update mark_victim tracepoints fields
config: x86_64-rhel-8.3-rust
(https://download.01.org/0day-ci/archive/20240111/202401112057.ljyusjje-...@intel.com/config)
compiler: ClangBuiltLinux clang version 17.0.6
(https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20240111/202401112057.ljyusjje-...@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/202401112057.ljyusjje-...@intel.com/
All errors (new ones prefixed by >>):
In file included from mm/oom_kill.c:54:
In file included from include/trace/events/oom.h:206:
In file included from include/trace/define_trace.h:102:
In file included from include/trace/trace_events.h:237:
>> include/trace/events/oom.h:96:3: error: called object type 'uid_t' (aka
>> 'unsigned int') is not a function or function pointer
74 | ),
| ~~
75 |
76 | TP_fast_assign(
| ~~~
77 | __entry->pid = task->pid;
| ~
78 | __entry->uid = uid;
| ~~~
79 | __assign_str(comm, task->comm);
| ~~~
80 | __entry->oom_score_adj = task->signal->oom_score_adj;
| ~
81 | ),
| ~~
82 |
83 | TP_printk("pid=%d uid=%u comm=%s oom_score_adj=%hd",
|
84 | __entry->pid,
| ~
85 | __entry->uid
|
86 | __get_str(comm),
| ^~~~
87 | __entry->oom_score_adj,
| ~~~
88 | )
| ~
89 | );
| ~
include/trace/stages/stage3_trace_output.h:20:26: note: expanded from macro
'__get_str'
20 | #define __get_str(field) ((char *)__get_dynamic_array(field))
| ^
include/trace/stages/stage3_trace_output.h:9:43: note: expanded from macro
'TP_printk'
9 | #define TP_printk(fmt, args...) fmt "\n", args
| ^
include/trace/trace_events.h:45:16: note: expanded from macro 'TRACE_EVENT'
40 | DECLARE_EVENT_CLASS(name, \
|
41 | PARAMS(proto),\
| ~~~
42 | PARAMS(args), \
| ~~~
43 | PARAMS(tstruct), \
| ~~~
44 | PARAMS(assign), \
| ~~~
45 | PARAMS(print)); \
| ~~~^~~
include/linux/tracepoint.h:107:25: note: expanded from macro 'PARAMS'
107 | #define PARAMS(args...) args
| ^
include/trace/trace_events.h:203:27: note: expanded from macro
'DECLARE_EVENT_CLASS'
203 | trace_event_printf(iter, print);
\
| ^
In file included from mm/oom_kill.c:54:
In file included from include/trace/events/oom.h:206:
In file included from include/trace/define_trace.h:102:
In file included from include/trace/trace_events.h:237:
>> include/trace/events/oom.h:74:1: error: expected expression
74 | TRACE_EVENT(mark_victim,
| ^
include/trace/trace_events.h:40:2: note: expanded from macro 'TRACE_EVENT'
40 | DECLARE_EVENT_CLASS(
Re: [PATCH 5/5] LoongArch: Add pv ipi support on LoongArch system
Hi Bibo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 610a9b8f49fbcf1100716370d3b5f6f884a2835a]
url:
https://github.com/intel-lab-lkp/linux/commits/Bibo-Mao/LoongArch-KVM-Add-hypercall-instruction-emulation-support/20240103-151946
base: 610a9b8f49fbcf1100716370d3b5f6f884a2835a
patch link:
https://lore.kernel.org/r/20240103071615.3422264-6-maobibo%40loongson.cn
patch subject: [PATCH 5/5] LoongArch: Add pv ipi support on LoongArch system
config: loongarch-randconfig-r061-20240109
(https://download.01.org/0day-ci/archive/20240109/202401091354.gtbergqj-...@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
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/202401091354.gtbergqj-...@intel.com/
cocci warnings: (new ones prefixed by >>)
>> arch/loongarch/kvm/exit.c:681:5-8: Unneeded variable: "ret". Return " 0" on
>> line 701
--
>> arch/loongarch/kvm/exit.c:720:2-3: Unneeded semicolon
vim +681 arch/loongarch/kvm/exit.c
678
679 static int kvm_pv_send_ipi(struct kvm_vcpu *vcpu, int sgi)
680 {
> 681 int ret = 0;
682 u64 ipi_bitmap;
683 unsigned int min, cpu;
684 struct kvm_vcpu *dest;
685
686 ipi_bitmap = vcpu->arch.gprs[LOONGARCH_GPR_A1];
687 min = vcpu->arch.gprs[LOONGARCH_GPR_A2];
688
689 if (ipi_bitmap) {
690 cpu = find_first_bit((void *)_bitmap,
BITS_PER_LONG);
691 while (cpu < BITS_PER_LONG) {
692 if ((cpu + min) < KVM_MAX_VCPUS) {
693 dest = kvm_get_vcpu_by_id(vcpu->kvm,
cpu + min);
694 kvm_queue_irq(dest, sgi);
695 kvm_vcpu_kick(dest);
696 }
697 cpu = find_next_bit((void *)_bitmap,
BITS_PER_LONG, cpu + 1);
698 }
699 }
700
> 701 return ret;
702 }
703
704 /*
705 * hypcall emulation always return to guest, Caller should check retval.
706 */
707 static void kvm_handle_pv_hcall(struct kvm_vcpu *vcpu)
708 {
709 unsigned long func = vcpu->arch.gprs[LOONGARCH_GPR_A0];
710 long ret;
711
712 switch (func) {
713 case KVM_HC_FUNC_IPI:
714 kvm_pv_send_ipi(vcpu, INT_SWI0);
715 ret = KVM_HC_STATUS_SUCCESS;
716 break;
717 default:
718 ret = KVM_HC_INVALID_CODE;
719 break;
> 720 };
721
722 vcpu->arch.gprs[LOONGARCH_GPR_A0] = ret;
723 }
724
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH next v2 2/5] locking/osq_lock: Optimise the vcpu_is_preempted() check.
Hello,
kernel test robot noticed a 10.7% improvement of
stress-ng.netlink-task.ops_per_sec on:
commit: d93300891f810c9498d09a6ecea2403d7a3546f0 ("[PATCH next v2 2/5]
locking/osq_lock: Optimise the vcpu_is_preempted() check.")
url:
https://github.com/intel-lab-lkp/linux/commits/David-Laight/locking-osq_lock-Defer-clearing-node-locked-until-the-slow-osq_lock-path/20240101-055853
base: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git
610a9b8f49fbcf1100716370d3b5f6f884a2835a
patch link:
https://lore.kernel.org/all/3a9d1782cd50436c99ced8c10175b...@acums.aculab.com/
patch subject: [PATCH next v2 2/5] locking/osq_lock: Optimise the
vcpu_is_preempted() check.
testcase: stress-ng
test machine: 64 threads 2 sockets Intel(R) Xeon(R) Gold 6346 CPU @ 3.10GHz
(Ice Lake) with 256G memory
parameters:
nr_threads: 100%
testtime: 60s
sc_pid_max: 4194304
class: scheduler
test: netlink-task
cpufreq_governor: performance
Details are as below:
-->
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240108/202401081557.641738f5-oliver.s...@intel.com
=
class/compiler/cpufreq_governor/kconfig/nr_threads/rootfs/sc_pid_max/tbox_group/test/testcase/testtime:
scheduler/gcc-12/performance/x86_64-rhel-8.3/100%/debian-11.1-x86_64-20220510.cgz/4194304/lkp-icl-2sp8/netlink-task/stress-ng/60s
commit:
ff787c1fd0 ("locking/osq_lock: Defer clearing node->locked until the slow
osq_lock() path.")
d93300891f ("locking/osq_lock: Optimise the vcpu_is_preempted() check.")
ff787c1fd0c13f9b d93300891f810c9498d09a6ecea
---
%stddev %change %stddev
\ |\
3880 ± 7% +26.4% 4903 ± 18% vmstat.system.cs
0.48 ±126% -99.8% 0.00 ±141%
perf-sched.sch_delay.avg.ms.__cond_resched.aa_sk_perm.security_socket_recvmsg.sock_recvmsg.__sys_recvfrom
0.16 ± 23% -38.9% 0.10 ± 32%
perf-sched.sch_delay.avg.ms.schedule_preempt_disabled.__mutex_lock.constprop.0.genl_rcv_msg
1.50 ±118% -99.9% 0.00 ±142%
perf-sched.sch_delay.max.ms.__cond_resched.aa_sk_perm.security_socket_recvmsg.sock_recvmsg.__sys_recvfrom
2.55 ± 97% -83.7% 0.42 ±145%
perf-sched.wait_time.max.ms.__cond_resched.__mutex_lock.constprop.0.genl_rcv_msg
32244865 +10.7% 35709040stress-ng.netlink-task.ops
537413 +10.7% 595150stress-ng.netlink-task.ops_per_sec
38094 ± 12% +42.2% 54160 ± 27%
stress-ng.time.involuntary_context_switches
42290 ± 11% +39.8% 59117 ± 23%
stress-ng.time.voluntary_context_switches
143.50 ± 7% -28.8% 102.17 ± 15% perf-c2c.DRAM.local
4955 ± 3% -26.4% 3647 ± 4% perf-c2c.DRAM.remote
4038 ± 2% -18.8% 3277 ± 4% perf-c2c.HITM.local
3483 ± 3% -21.1% 2747 ± 5% perf-c2c.HITM.remote
7521 ± 2% -19.9% 6024 ± 4% perf-c2c.HITM.total
0.42 ± 3% -16.2% 0.35 ± 5% perf-stat.i.MPKI
1.066e+10+9.6% 1.169e+10perf-stat.i.branch-instructions
51.90-2.5 49.42 ± 2% perf-stat.i.cache-miss-rate%
22517746 ± 3% -13.4% 19503564 ± 5% perf-stat.i.cache-misses
3730 ± 7% +29.2% 4819 ± 19% perf-stat.i.context-switches
3.99-3.1% 3.86perf-stat.i.cpi
9535 ± 3% +15.4% 11003 ± 5%
perf-stat.i.cycles-between-cache-misses
0.00 ± 3% +0.00.00 ± 3% perf-stat.i.dTLB-load-miss-rate%
1.419e+10 -14.9% 1.207e+10perf-stat.i.dTLB-loads
8.411e+08+8.4% 9.118e+08perf-stat.i.dTLB-stores
5.36e+10+3.1% 5.524e+10perf-stat.i.instructions
0.26+7.0% 0.28 ± 5% perf-stat.i.ipc
837.29 ± 3% -9.8% 755.30 ± 4% perf-stat.i.metric.K/sec
401.41-4.1% 385.10perf-stat.i.metric.M/sec
6404966 -23.2%4920722perf-stat.i.node-load-misses
141818 ± 4% -22.2% 110404 ± 4% perf-stat.i.node-loads
69.54 +13.8 83.36perf-stat.i.node-store-miss-rate%
3935319 +10.4%4345724perf-stat.i.node-store-misses
1626033 -52.6% 771187 ± 5% perf-stat.i.node-stores
0.42 ± 3% -16.0% 0.35 ± 5% perf-stat.overall.MPKI
0.11-0.00.10 ± 8%
perf-stat.overall.branch-miss-rate%
51.32-2.5 48.79 ± 2% perf-stat.overall.cache-miss-rate%
4.06-3.0% 3.94perf-stat.overall.cpi
9677 ± 3
Re: [PATCH 3/5] LoongArch/smp: Refine ipi ops on LoongArch platform
Hi Bibo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 610a9b8f49fbcf1100716370d3b5f6f884a2835a]
url:
https://github.com/intel-lab-lkp/linux/commits/Bibo-Mao/LoongArch-KVM-Add-hypercall-instruction-emulation-support/20240103-151946
base: 610a9b8f49fbcf1100716370d3b5f6f884a2835a
patch link:
https://lore.kernel.org/r/20240103071615.3422264-4-maobibo%40loongson.cn
patch subject: [PATCH 3/5] LoongArch/smp: Refine ipi ops on LoongArch platform
config: loongarch-randconfig-r131-20240103
(https://download.01.org/0day-ci/archive/20240104/202401040952.1jdpfc85-...@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce:
(https://download.01.org/0day-ci/archive/20240104/202401040952.1jdpfc85-...@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/202401040952.1jdpfc85-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/loongarch/kernel/smp.c:192:73: sparse: sparse: incorrect type in
>> argument 4 (different address spaces) @@ expected void [noderef]
>> __percpu *percpu_dev_id @@ got int * @@
arch/loongarch/kernel/smp.c:192:73: sparse: expected void [noderef]
__percpu *percpu_dev_id
arch/loongarch/kernel/smp.c:192:73: sparse: got int *
arch/loongarch/kernel/smp.c: note: in included file (through
arch/loongarch/include/asm/loongarch.h, arch/loongarch/include/asm/cpu-info.h,
...):
../lib/gcc/loongarch64-linux/13.2.0/include/larchintrin.h:332:3: sparse:
sparse: undefined identifier '__builtin_loongarch_iocsrwr_d'
../lib/gcc/loongarch64-linux/13.2.0/include/larchintrin.h:284:25: sparse:
sparse: undefined identifier '__builtin_loongarch_iocsrrd_w'
../lib/gcc/loongarch64-linux/13.2.0/include/larchintrin.h:284:11: sparse:
sparse: cast from unknown type
../lib/gcc/loongarch64-linux/13.2.0/include/larchintrin.h:322:3: sparse:
sparse: undefined identifier '__builtin_loongarch_iocsrwr_w'
arch/loongarch/kernel/smp.c: note: in included file (through
arch/loongarch/include/asm/cpu-info.h, arch/loongarch/include/asm/processor.h,
...):
arch/loongarch/include/asm/loongarch.h:1260:1: sparse: sparse: undefined
identifier '__builtin_loongarch_csrrd_w'
arch/loongarch/include/asm/loongarch.h:1260:1: sparse: sparse: cast from
unknown type
arch/loongarch/include/asm/loongarch.h:1260:1: sparse: sparse: undefined
identifier '__builtin_loongarch_csrwr_w'
arch/loongarch/include/asm/loongarch.h:1260:1: sparse: sparse: cast from
unknown type
arch/loongarch/include/asm/loongarch.h:1260:1: sparse: sparse: undefined
identifier '__builtin_loongarch_csrrd_w'
arch/loongarch/include/asm/loongarch.h:1260:1: sparse: sparse: cast from
unknown type
arch/loongarch/include/asm/loongarch.h:1260:1: sparse: sparse: undefined
identifier '__builtin_loongarch_csrwr_w'
arch/loongarch/include/asm/loongarch.h:1260:1: sparse: sparse: cast from
unknown type
arch/loongarch/include/asm/loongarch.h:1260:1: sparse: sparse: undefined
identifier '__builtin_loongarch_csrrd_w'
arch/loongarch/include/asm/loongarch.h:1260:1: sparse: sparse: cast from
unknown type
arch/loongarch/include/asm/loongarch.h:1260:1: sparse: sparse: undefined
identifier '__builtin_loongarch_csrwr_w'
arch/loongarch/include/asm/loongarch.h:1260:1: sparse: sparse: cast from
unknown type
arch/loongarch/kernel/smp.c: note: in included file (through
arch/loongarch/include/asm/loongarch.h, arch/loongarch/include/asm/cpu-info.h,
...):
../lib/gcc/loongarch64-linux/13.2.0/include/larchintrin.h:294:30: sparse:
sparse: undefined identifier '__builtin_loongarch_iocsrrd_d'
../lib/gcc/loongarch64-linux/13.2.0/include/larchintrin.h:294:11: sparse:
sparse: cast from unknown type
arch/loongarch/kernel/smp.c: note: in included file (through
include/linux/irqflags.h, include/linux/spinlock.h, include/linux/mmzone.h,
...):
arch/loongarch/include/asm/percpu.h:30:9: sparse: sparse: undefined
identifier '__builtin_loongarch_csrwr_d'
arch/loongarch/include/asm/percpu.h:30:9: sparse: sparse: cast from unknown
type
arch/loongarch/include/asm/percpu.h:30:9: sparse: sparse: cast from unknown
type
vim +192 arch/loongarch/kernel/smp.c
181
182 static void loongson_ipi_init(void)
183 {
184 int r, ipi_irq;
185 static int ipi_dummy_dev;
186
187 ipi_irq = get_percpu_irq(INT_IPI);
188 if (ipi_irq < 0)
189 panic("IPI IRQ mapping failed\n");
190
191 irq_set_percpu_devid(ipi_irq);
> 192 r = request_percpu_irq(ipi_irq, loongson_ipi_interrupt, "IPI",
> _dummy_dev);
193 if (r < 0)
194 panic("IPI IRQ request failed\n");
195 }
196
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH net-next v3 3/3] net: add netmem_ref to skb_frag_t
Hi Mina, kernel test robot noticed the following build warnings: [auto build test WARNING on net-next/main] url: https://github.com/intel-lab-lkp/linux/commits/Mina-Almasry/vsock-virtio-use-skb_frag_-helpers/20231222-164637 base: net-next/main patch link: https://lore.kernel.org/r/20231220214505.2303297-4-almasrymina%40google.com patch subject: [PATCH net-next v3 3/3] net: add netmem_ref to skb_frag_t :: branch date: 15 hours ago :: commit date: 15 hours ago config: x86_64-randconfig-121-20231223 (https://download.01.org/0day-ci/archive/20231223/202312230726.4xapn84e-...@intel.com/config) compiler: gcc-11 (Debian 11.3.0-12) 11.3.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231223/202312230726.4xapn84e-...@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/r/202312230726.4xapn84e-...@intel.com/ sparse warnings: (new ones prefixed by >>) net/core/netevent.c: note: in included file (through include/linux/skbuff.h, include/net/net_namespace.h, include/linux/netdevice.h, ...): >> include/net/netmem.h:28:54: sparse: sparse: invalid modifier include/net/netmem.h:36:26: sparse: sparse: invalid modifier include/net/netmem.h:38:27: sparse: sparse: invalid modifier net/core/netevent.c: note: in included file (through include/net/net_namespace.h, include/linux/netdevice.h, include/linux/rtnetlink.h): >> include/linux/skbuff.h:364:20: sparse: sparse: invalid modifier include/linux/skbuff.h:2440:57: sparse: sparse: invalid modifier include/linux/skbuff.h:2456:67: sparse: sparse: invalid modifier include/linux/skbuff.h:2498:54: sparse: sparse: invalid modifier include/linux/skbuff.h:2521:52: sparse: sparse: invalid modifier include/linux/skbuff.h:2571:68: sparse: sparse: invalid modifier -- net/core/request_sock.c: note: in included file (through include/linux/skbuff.h, include/linux/tcp.h): >> include/net/netmem.h:28:54: sparse: sparse: invalid modifier include/net/netmem.h:36:26: sparse: sparse: invalid modifier include/net/netmem.h:38:27: sparse: sparse: invalid modifier net/core/request_sock.c: note: in included file (through include/linux/tcp.h): >> include/linux/skbuff.h:364:20: sparse: sparse: invalid modifier include/linux/skbuff.h:2440:57: sparse: sparse: invalid modifier include/linux/skbuff.h:2456:67: sparse: sparse: invalid modifier include/linux/skbuff.h:2498:54: sparse: sparse: invalid modifier include/linux/skbuff.h:2521:52: sparse: sparse: invalid modifier include/linux/skbuff.h:2571:68: sparse: sparse: invalid modifier -- net/core/utils.c: note: in included file (through include/linux/skbuff.h, include/net/net_namespace.h, include/linux/inet.h): >> include/net/netmem.h:28:54: sparse: sparse: invalid modifier include/net/netmem.h:36:26: sparse: sparse: invalid modifier include/net/netmem.h:38:27: sparse: sparse: invalid modifier net/core/utils.c: note: in included file (through include/net/net_namespace.h, include/linux/inet.h): >> include/linux/skbuff.h:364:20: sparse: sparse: invalid modifier include/linux/skbuff.h:2440:57: sparse: sparse: invalid modifier include/linux/skbuff.h:2456:67: sparse: sparse: invalid modifier include/linux/skbuff.h:2498:54: sparse: sparse: invalid modifier include/linux/skbuff.h:2521:52: sparse: sparse: invalid modifier include/linux/skbuff.h:2571:68: sparse: sparse: invalid modifier -- net/core/secure_seq.c: note: in included file (through include/linux/skbuff.h, include/linux/tcp.h, include/net/tcp.h): >> include/net/netmem.h:28:54: sparse: sparse: invalid modifier include/net/netmem.h:36:26: sparse: sparse: invalid modifier include/net/netmem.h:38:27: sparse: sparse: invalid modifier net/core/secure_seq.c: note: in included file (through include/linux/tcp.h, include/net/tcp.h): >> include/linux/skbuff.h:364:20: sparse: sparse: invalid modifier include/linux/skbuff.h:2440:57: sparse: sparse: invalid modifier include/linux/skbuff.h:2456:67: sparse: sparse: invalid modifier include/linux/skbuff.h:2498:54: sparse: sparse: invalid modifier include/linux/skbuff.h:2521:52: sparse: sparse: invalid modifier include/linux/skbuff.h:2571:68: sparse: sparse: invalid modifier -- net/core/net_namespace.c: note: in included file (through include/linux/skbuff.h, include/net/net_namespace.h, include/linux/netdevice.h, ...): >> include/net/netmem.h:28:54: sparse: sparse: invalid modifier include/net/netmem.h:36:26: sparse: sparse: invalid modifier include/net/netmem.h:38:27: sparse: sparse: invalid modifier net/core/net_namespace.c: note: in included file (through include/net/net_namespace.h, include/linux/netdevice.h, include/linux/rtnetlink.h): >> include/linux/skbuff.h:
Re: [PATCH bpf-next 1/3] bpf: implement relay map basis
Hi Philo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on bpf-next/master]
url:
https://github.com/intel-lab-lkp/linux/commits/Philo-Lu/bpf-implement-relay-map-basis/20231222-204545
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link:
https://lore.kernel.org/r/20231222122146.65519-2-lulie%40linux.alibaba.com
patch subject: [PATCH bpf-next 1/3] bpf: implement relay map basis
config: x86_64-kexec
(https://download.01.org/0day-ci/archive/20231223/202312230850.nqeizxj6-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231223/202312230850.nqeizxj6-...@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/202312230850.nqeizxj6-...@intel.com/
All warnings (new ones prefixed by >>):
kernel/bpf/relaymap.c: In function 'relay_map_alloc':
>> kernel/bpf/relaymap.c:79:13: warning: the comparison will always evaluate as
>> 'true' for the address of 'map_name' will never be NULL [-Waddress]
79 | if (!attr->map_name || strlen(attr->map_name) == 0)
| ^
In file included from include/linux/bpf.h:7,
from include/linux/filter.h:9,
from kernel/bpf/relaymap.c:3:
include/uapi/linux/bpf.h:1394:25: note: 'map_name' declared here
1394 | charmap_name[BPF_OBJ_NAME_LEN];
| ^~~~
vim +79 kernel/bpf/relaymap.c
43
44 /* bpf_attr is used as follows:
45 * - key size: must be 0
46 * - value size: value will be used as directory name by map_update_elem
47 * (to create relay files). If passed as 0, it will be set to
NAME_MAX as
48 * default
49 *
50 * - max_entries: subbuf size
51 * - map_extra: subbuf num, default as 8
52 *
53 * When alloc, we do not set up relay files considering dir_name
conflicts.
54 * Instead we use relay_late_setup_files() in map_update_elem(), and
thus the
55 * value is used as dir_name, and map->name is used as base_filename.
56 */
57 static struct bpf_map *relay_map_alloc(union bpf_attr *attr)
58 {
59 struct bpf_relay_map *rmap;
60
61 if (unlikely(attr->map_flags & ~RELAY_CREATE_FLAG_MASK))
62 return ERR_PTR(-EINVAL);
63
64 /* key size must be 0 in relay map */
65 if (unlikely(attr->key_size))
66 return ERR_PTR(-EINVAL);
67
68 if (unlikely(attr->value_size > NAME_MAX)) {
69 pr_warn("value_size should be no more than %d\n",
NAME_MAX);
70 return ERR_PTR(-EINVAL);
71 } else if (attr->value_size == 0)
72 attr->value_size = NAME_MAX;
73
74 /* set default subbuf num */
75 attr->map_extra = attr->map_extra & UINT_MAX;
76 if (!attr->map_extra)
77 attr->map_extra = 8;
78
> 79 if (!attr->map_name || strlen(attr->map_name) == 0)
80 return ERR_PTR(-EINVAL);
81
82 rmap = bpf_map_area_alloc(sizeof(*rmap), NUMA_NO_NODE);
83 if (!rmap)
84 return ERR_PTR(-ENOMEM);
85
86 bpf_map_init_from_attr(>map, attr);
87
88 rmap->relay_cb.create_buf_file = create_buf_file_handler;
89 rmap->relay_cb.remove_buf_file = remove_buf_file_handler;
90 if (attr->map_flags & BPF_F_OVERWRITE)
91 rmap->relay_cb.subbuf_start = subbuf_start_overwrite;
92
93 rmap->relay_chan = relay_open(NULL, NULL,
94
attr->max_entries, attr->map_extra,
95
>relay_cb, NULL);
96 if (!rmap->relay_chan)
97 return ERR_PTR(-EINVAL);
98
99 return >map;
100 }
101
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH net-next v3 3/3] net: add netmem_ref to skb_frag_t
Hi Mina,
kernel test robot noticed the following build errors:
[auto build test ERROR on net-next/main]
url:
https://github.com/intel-lab-lkp/linux/commits/Mina-Almasry/vsock-virtio-use-skb_frag_-helpers/20231222-164637
base: net-next/main
patch link:
https://lore.kernel.org/r/20231220214505.2303297-4-almasrymina%40google.com
patch subject: [PATCH net-next v3 3/3] net: add netmem_ref to skb_frag_t
config: i386-randconfig-141-20231222
(https://download.01.org/0day-ci/archive/20231223/202312230739.g0tfssdt-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231223/202312230739.g0tfssdt-...@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/202312230739.g0tfssdt-...@intel.com/
All errors (new ones prefixed by >>):
net/kcm/kcmsock.c: In function 'kcm_write_msgs':
>> net/kcm/kcmsock.c:637:59: error: 'skb_frag_t' {aka 'struct skb_frag'} has no
>> member named 'bv_len'
637 | msize += skb_shinfo(skb)->frags[i].bv_len;
| ^
vim +637 net/kcm/kcmsock.c
cd6e111bf5be5c Tom Herbert 2016-03-07 578
ab7ac4eb9832e3 Tom Herbert 2016-03-07 579 /* Write any messages ready
on the kcm socket. Called with kcm sock lock
ab7ac4eb9832e3 Tom Herbert 2016-03-07 580 * held. Return bytes
actually sent or error.
ab7ac4eb9832e3 Tom Herbert 2016-03-07 581 */
ab7ac4eb9832e3 Tom Herbert 2016-03-07 582 static int
kcm_write_msgs(struct kcm_sock *kcm)
ab7ac4eb9832e3 Tom Herbert 2016-03-07 583 {
c31a25e1db486f David Howells 2023-06-09 584unsigned int total_sent
= 0;
ab7ac4eb9832e3 Tom Herbert 2016-03-07 585struct sock *sk =
>sk;
ab7ac4eb9832e3 Tom Herbert 2016-03-07 586struct kcm_psock *psock;
c31a25e1db486f David Howells 2023-06-09 587struct sk_buff *head;
ab7ac4eb9832e3 Tom Herbert 2016-03-07 588int ret = 0;
ab7ac4eb9832e3 Tom Herbert 2016-03-07 589
ab7ac4eb9832e3 Tom Herbert 2016-03-07 590kcm->tx_wait_more =
false;
ab7ac4eb9832e3 Tom Herbert 2016-03-07 591psock = kcm->tx_psock;
ab7ac4eb9832e3 Tom Herbert 2016-03-07 592if (unlikely(psock &&
psock->tx_stopped)) {
ab7ac4eb9832e3 Tom Herbert 2016-03-07 593/* A reserved
psock was aborted asynchronously. Unreserve
ab7ac4eb9832e3 Tom Herbert 2016-03-07 594 * it and we'll
retry the message.
ab7ac4eb9832e3 Tom Herbert 2016-03-07 595 */
ab7ac4eb9832e3 Tom Herbert 2016-03-07 596
unreserve_psock(kcm);
cd6e111bf5be5c Tom Herbert 2016-03-07 597
kcm_report_tx_retry(kcm);
ab7ac4eb9832e3 Tom Herbert 2016-03-07 598if
(skb_queue_empty(>sk_write_queue))
ab7ac4eb9832e3 Tom Herbert 2016-03-07 599return
0;
ab7ac4eb9832e3 Tom Herbert 2016-03-07 600
c31a25e1db486f David Howells 2023-06-09 601
kcm_tx_msg(skb_peek(>sk_write_queue))->started_tx = false;
ab7ac4eb9832e3 Tom Herbert 2016-03-07 602}
ab7ac4eb9832e3 Tom Herbert 2016-03-07 603
c31a25e1db486f David Howells 2023-06-09 604 retry:
c31a25e1db486f David Howells 2023-06-09 605while ((head =
skb_peek(>sk_write_queue))) {
c31a25e1db486f David Howells 2023-06-09 606struct msghdr
msg = {
c31a25e1db486f David Howells 2023-06-09 607
.msg_flags = MSG_DONTWAIT | MSG_SPLICE_PAGES,
c31a25e1db486f David Howells 2023-06-09 608};
c31a25e1db486f David Howells 2023-06-09 609struct
kcm_tx_msg *txm = kcm_tx_msg(head);
c31a25e1db486f David Howells 2023-06-09 610struct sk_buff
*skb;
c31a25e1db486f David Howells 2023-06-09 611unsigned int
msize;
c31a25e1db486f David Howells 2023-06-09 612int i;
ab7ac4eb9832e3 Tom Herbert 2016-03-07 613
c31a25e1db486f David Howells 2023-06-09 614if
(!txm->started_tx) {
c31a25e1db486f David Howells 2023-06-09 615psock =
reserve_psock(kcm);
c31a25e1db486f David Howells 2023-06-09 616if
(!psock)
c31a25e1db486f David Howells 2023-06-09 617
goto out;
c31a25e1db486f David Howells 2023-06-09 618skb =
head;
c31a25e1db486f David Howells 2023-06-09 619
txm->frag_offset = 0;
c31a25e1db486f David Howells 2023-06-09 620
txm-
Re: [PATCH bpf-next 1/3] bpf: implement relay map basis
Hi Philo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on bpf-next/master]
url:
https://github.com/intel-lab-lkp/linux/commits/Philo-Lu/bpf-implement-relay-map-basis/20231222-204545
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link:
https://lore.kernel.org/r/20231222122146.65519-2-lulie%40linux.alibaba.com
patch subject: [PATCH bpf-next 1/3] bpf: implement relay map basis
config: arm-randconfig-001-20231223
(https://download.01.org/0day-ci/archive/20231223/202312230638.iydd8joz-...@intel.com/config)
compiler: clang version 18.0.0git (https://github.com/llvm/llvm-project
d3ef86708241a3bee902615c190dead1638c4e09)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231223/202312230638.iydd8joz-...@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/202312230638.iydd8joz-...@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/bpf/relaymap.c:79:13: warning: address of array 'attr->map_name' will
>> always evaluate to 'true' [-Wpointer-bool-conversion]
79 | if (!attr->map_name || strlen(attr->map_name) == 0)
| ~~~^~~~
1 warning generated.
vim +79 kernel/bpf/relaymap.c
43
44 /* bpf_attr is used as follows:
45 * - key size: must be 0
46 * - value size: value will be used as directory name by map_update_elem
47 * (to create relay files). If passed as 0, it will be set to
NAME_MAX as
48 * default
49 *
50 * - max_entries: subbuf size
51 * - map_extra: subbuf num, default as 8
52 *
53 * When alloc, we do not set up relay files considering dir_name
conflicts.
54 * Instead we use relay_late_setup_files() in map_update_elem(), and
thus the
55 * value is used as dir_name, and map->name is used as base_filename.
56 */
57 static struct bpf_map *relay_map_alloc(union bpf_attr *attr)
58 {
59 struct bpf_relay_map *rmap;
60
61 if (unlikely(attr->map_flags & ~RELAY_CREATE_FLAG_MASK))
62 return ERR_PTR(-EINVAL);
63
64 /* key size must be 0 in relay map */
65 if (unlikely(attr->key_size))
66 return ERR_PTR(-EINVAL);
67
68 if (unlikely(attr->value_size > NAME_MAX)) {
69 pr_warn("value_size should be no more than %d\n",
NAME_MAX);
70 return ERR_PTR(-EINVAL);
71 } else if (attr->value_size == 0)
72 attr->value_size = NAME_MAX;
73
74 /* set default subbuf num */
75 attr->map_extra = attr->map_extra & UINT_MAX;
76 if (!attr->map_extra)
77 attr->map_extra = 8;
78
> 79 if (!attr->map_name || strlen(attr->map_name) == 0)
80 return ERR_PTR(-EINVAL);
81
82 rmap = bpf_map_area_alloc(sizeof(*rmap), NUMA_NO_NODE);
83 if (!rmap)
84 return ERR_PTR(-ENOMEM);
85
86 bpf_map_init_from_attr(>map, attr);
87
88 rmap->relay_cb.create_buf_file = create_buf_file_handler;
89 rmap->relay_cb.remove_buf_file = remove_buf_file_handler;
90 if (attr->map_flags & BPF_F_OVERWRITE)
91 rmap->relay_cb.subbuf_start = subbuf_start_overwrite;
92
93 rmap->relay_chan = relay_open(NULL, NULL,
94
attr->max_entries, attr->map_extra,
95
>relay_cb, NULL);
96 if (!rmap->relay_chan)
97 return ERR_PTR(-EINVAL);
98
99 return >map;
100 }
101
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH net-next v3 3/3] net: add netmem_ref to skb_frag_t
Hi Mina,
kernel test robot noticed the following build errors:
[auto build test ERROR on net-next/main]
url:
https://github.com/intel-lab-lkp/linux/commits/Mina-Almasry/vsock-virtio-use-skb_frag_-helpers/20231222-164637
base: net-next/main
patch link:
https://lore.kernel.org/r/20231220214505.2303297-4-almasrymina%40google.com
patch subject: [PATCH net-next v3 3/3] net: add netmem_ref to skb_frag_t
config: powerpc-allmodconfig
(https://download.01.org/0day-ci/archive/20231223/202312230340.icf8soop-...@intel.com/config)
compiler: clang version 18.0.0git (https://github.com/llvm/llvm-project
d3ef86708241a3bee902615c190dead1638c4e09)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231223/202312230340.icf8soop-...@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/202312230340.icf8soop-...@intel.com/
All errors (new ones prefixed by >>):
>> net/kcm/kcmsock.c:637:39: error: no member named 'bv_len' in 'struct
>> skb_frag'
637 | msize += skb_shinfo(skb)->frags[i].bv_len;
| ~ ^
1 error generated.
vim +637 net/kcm/kcmsock.c
cd6e111bf5be5c Tom Herbert 2016-03-07 578
ab7ac4eb9832e3 Tom Herbert 2016-03-07 579 /* Write any messages ready
on the kcm socket. Called with kcm sock lock
ab7ac4eb9832e3 Tom Herbert 2016-03-07 580 * held. Return bytes
actually sent or error.
ab7ac4eb9832e3 Tom Herbert 2016-03-07 581 */
ab7ac4eb9832e3 Tom Herbert 2016-03-07 582 static int
kcm_write_msgs(struct kcm_sock *kcm)
ab7ac4eb9832e3 Tom Herbert 2016-03-07 583 {
c31a25e1db486f David Howells 2023-06-09 584unsigned int total_sent
= 0;
ab7ac4eb9832e3 Tom Herbert 2016-03-07 585struct sock *sk =
>sk;
ab7ac4eb9832e3 Tom Herbert 2016-03-07 586struct kcm_psock *psock;
c31a25e1db486f David Howells 2023-06-09 587struct sk_buff *head;
ab7ac4eb9832e3 Tom Herbert 2016-03-07 588int ret = 0;
ab7ac4eb9832e3 Tom Herbert 2016-03-07 589
ab7ac4eb9832e3 Tom Herbert 2016-03-07 590kcm->tx_wait_more =
false;
ab7ac4eb9832e3 Tom Herbert 2016-03-07 591psock = kcm->tx_psock;
ab7ac4eb9832e3 Tom Herbert 2016-03-07 592if (unlikely(psock &&
psock->tx_stopped)) {
ab7ac4eb9832e3 Tom Herbert 2016-03-07 593/* A reserved
psock was aborted asynchronously. Unreserve
ab7ac4eb9832e3 Tom Herbert 2016-03-07 594 * it and we'll
retry the message.
ab7ac4eb9832e3 Tom Herbert 2016-03-07 595 */
ab7ac4eb9832e3 Tom Herbert 2016-03-07 596
unreserve_psock(kcm);
cd6e111bf5be5c Tom Herbert 2016-03-07 597
kcm_report_tx_retry(kcm);
ab7ac4eb9832e3 Tom Herbert 2016-03-07 598if
(skb_queue_empty(>sk_write_queue))
ab7ac4eb9832e3 Tom Herbert 2016-03-07 599return
0;
ab7ac4eb9832e3 Tom Herbert 2016-03-07 600
c31a25e1db486f David Howells 2023-06-09 601
kcm_tx_msg(skb_peek(>sk_write_queue))->started_tx = false;
ab7ac4eb9832e3 Tom Herbert 2016-03-07 602}
ab7ac4eb9832e3 Tom Herbert 2016-03-07 603
c31a25e1db486f David Howells 2023-06-09 604 retry:
c31a25e1db486f David Howells 2023-06-09 605while ((head =
skb_peek(>sk_write_queue))) {
c31a25e1db486f David Howells 2023-06-09 606struct msghdr
msg = {
c31a25e1db486f David Howells 2023-06-09 607
.msg_flags = MSG_DONTWAIT | MSG_SPLICE_PAGES,
c31a25e1db486f David Howells 2023-06-09 608};
c31a25e1db486f David Howells 2023-06-09 609struct
kcm_tx_msg *txm = kcm_tx_msg(head);
c31a25e1db486f David Howells 2023-06-09 610struct sk_buff
*skb;
c31a25e1db486f David Howells 2023-06-09 611unsigned int
msize;
c31a25e1db486f David Howells 2023-06-09 612int i;
ab7ac4eb9832e3 Tom Herbert 2016-03-07 613
c31a25e1db486f David Howells 2023-06-09 614if
(!txm->started_tx) {
c31a25e1db486f David Howells 2023-06-09 615psock =
reserve_psock(kcm);
c31a25e1db486f David Howells 2023-06-09 616if
(!psock)
c31a25e1db486f David Howells 2023-06-09 617
goto out;
c31a25e1db486f David Howells 2023-06-09 618skb =
head;
c31a25e1db486f David Howells 2023-06-09 619
txm->frag_offset = 0;
c31a25e1db486f David Howells 2023-06-09 620
[mhiramat:topic/fprobe-on-fgraph] [function_graph] b92a5e78c3: WARNING:at_kernel/trace/trace.c:#run_tracer_selftest
Hello,
kernel test robot noticed
"WARNING:at_kernel/trace/trace.c:#run_tracer_selftest" on:
commit: b92a5e78c35fde3c1be7263b39724388482a4bd9 ("function_graph: Add a new
entry handler with parent_ip and ftrace_regs")
https://git.kernel.org/cgit/linux/kernel/git/mhiramat/linux.git
topic/fprobe-on-fgraph
in testcase: trinity
version: trinity-i386-abe9de86-1_20230429
with following parameters:
runtime: 600s
test-description: Trinity is a linux system call fuzz tester.
test-url: http://codemonkey.org.uk/projects/trinity/
compiler: gcc-12
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+--+++
|
| 26fcffc6d7 | b92a5e78c3 |
+--+++
| WARNING:at_kernel/trace/trace.c:#run_tracer_selftest
| 0 | 8 |
| EIP:run_tracer_selftest
| 0 | 8 |
+--+++
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-lkp/202312181100.508f8f48-oliver.s...@intel.com
[5.502226][T1] [ cut here ]
[ 5.502226][ T1] WARNING: CPU: 1 PID: 1 at kernel/trace/trace.c:2031
run_tracer_selftest (kernel/trace/trace.c:2031 (discriminator 1))
[5.502899][T1] Modules linked in:
[5.503348][T1] CPU: 1 PID: 1 Comm: swapper/0 Not tainted
6.7.0-rc2-00034-gb92a5e78c35f #1
[5.504358][T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 5.505125][ T1] EIP: run_tracer_selftest (kernel/trace/trace.c:2031
(discriminator 1))
[ 5.505764][ T1] Code: ff ff a3 18 30 4b c2 89 f8 89 15 1c 30 4b c2 e8 cb b1 ff
ff 89 f8 e8 58 52 ff ff e9 c1 fe ff ff 68 50 d6 f9 c1 e8 2d 61 f7 ff <0f> 0b b8
ff ff ff ff 5a e9 22 ff ff ff b8 f4 ff ff ff e9 18 ff ff
All code
0: ff (bad)
1: ff a3 18 30 4b c2 jmp*-0x3db4cfe8(%rbx)
7: 89 f8 mov%edi,%eax
9: 89 15 1c 30 4b c2 mov%edx,-0x3db4cfe4(%rip)#
0xc24b302b
f: e8 cb b1 ff ff call 0xb1df
14: 89 f8 mov%edi,%eax
16: e8 58 52 ff ff call 0x5273
1b: e9 c1 fe ff ff jmp0xfee1
20: 68 50 d6 f9 c1 push $0xc1f9d650
25: e8 2d 61 f7 ff call 0xfff76157
2a:* 0f 0b ud2 <-- trapping instruction
2c: b8 ff ff ff ff mov$0x,%eax
31: 5a pop%rdx
32: e9 22 ff ff ff jmp0xff59
37: b8 f4 ff ff ff mov$0xfff4,%eax
3c: e9 .byte 0xe9
3d: 18 ff sbb%bh,%bh
3f: ff .byte 0xff
Code starting with the faulting instruction
===
0: 0f 0b ud2
2: b8 ff ff ff ff mov$0x,%eax
7: 5a pop%rdx
8: e9 22 ff ff ff jmp0xff2f
d: b8 f4 ff ff ff mov$0xfff4,%eax
12: e9 .byte 0xe9
13: 18 ff sbb%bh,%bh
15: ff .byte 0xff
[5.508031][T1] EAX: 0007 EBX: c1f9fa5b ECX: EDX:
[5.508856][T1] ESI: c25e18e0 EDI: c0109500 EBP: c031bed4 ESP: c031bec4
[5.513135][T1] DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 EFLAGS:
00010286
[5.514023][T1] CR0: 80050033 CR2: CR3: 02763000 CR4: 000406d0
[5.514855][T1] DR0: DR1: DR2: DR3:
[5.515688][T1] DR6: fffe0ff0 DR7: 0400
[5.516235][T1] Call Trace:
[ 5.516632][ T1] ? show_regs (arch/x86/kernel/dumpstack.c:479)
[ 5.517125][ T1] ? run_tracer_selftest (kernel/trace/trace.c:2031
(discriminator 1))
[ 5.517722][ T1] ? __warn (kernel/panic.c:677)
[ 5.518185][ T1] ? run_tracer_selftest (kernel/trace/trace.c:2031
(discriminator 1))
[ 5.518797][ T1] ? report_bug (lib/bug.c:201 lib/bug.c:219)
[ 5.519323][ T1] ? exc_overflow (arch/x86/kernel/traps.c:250)
[ 5.519844][ T1] ? handle_bug (arch/x86/kernel/traps.c:216)
[ 5.520351][ T1] ? exc_invalid_op (arch/x86/kernel/traps.c:258 (discriminator
1))
[ 5.521153][ T1] ? handle_exception (a
Re: [PATCH -next 2/2] mm: vmscan: add new event to trace shrink lru
Hi Bixuan,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20231211]
url:
https://github.com/intel-lab-lkp/linux/commits/Bixuan-Cui/mm-shrinker-add-new-event-to-trace-shrink-count/20231212-112824
base: next-20231211
patch link:
https://lore.kernel.org/r/20231212032640.6968-3-cuibixuan%40vivo.com
patch subject: [PATCH -next 2/2] mm: vmscan: add new event to trace shrink lru
config: i386-randconfig-014-20231214
(https://download.01.org/0day-ci/archive/20231215/202312150018.eie4fkef-...@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git
ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231215/202312150018.eie4fkef-...@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/202312150018.eie4fkef-...@intel.com/
All errors (new ones prefixed by >>):
>> mm/vmscan.c:4533:2: error: call to undeclared function
>> 'trace_mm_vmscan_lru_shrink_inactive'; ISO C99 and later do not support
>> implicit function declarations [-Wimplicit-function-declaration]
trace_mm_vmscan_lru_shrink_inactive(pgdat->node_id,
^
mm/vmscan.c:4533:2: note: did you mean
'trace_mm_vmscan_lru_shrink_inactive_end'?
include/trace/events/vmscan.h:415:1: note:
'trace_mm_vmscan_lru_shrink_inactive_end' declared here
TRACE_EVENT(mm_vmscan_lru_shrink_inactive_end,
^
include/linux/tracepoint.h:566:2: note: expanded from macro 'TRACE_EVENT'
DECLARE_TRACE(name, PARAMS(proto), PARAMS(args))
^
include/linux/tracepoint.h:432:2: note: expanded from macro 'DECLARE_TRACE'
__DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), \
^
include/linux/tracepoint.h:255:21: note: expanded from macro
'__DECLARE_TRACE'
static inline void trace_##name(proto) \
^
:60:1: note: expanded from here
trace_mm_vmscan_lru_shrink_inactive_end
^
1 error generated.
vim +/trace_mm_vmscan_lru_shrink_inactive +4533 mm/vmscan.c
ac35a490237446 Yu Zhao 2022-09-18 4500
a579086c99ed70 Yu Zhao 2022-12-21 4501 static int
evict_folios(struct lruvec *lruvec, struct scan_control *sc, int swappiness)
ac35a490237446 Yu Zhao 2022-09-18 4502 {
ac35a490237446 Yu Zhao 2022-09-18 4503 int type;
ac35a490237446 Yu Zhao 2022-09-18 4504 int scanned;
ac35a490237446 Yu Zhao 2022-09-18 4505 int reclaimed;
ac35a490237446 Yu Zhao 2022-09-18 4506 LIST_HEAD(list);
359a5e1416caaf Yu Zhao 2022-11-15 4507
LIST_HEAD(clean);
ac35a490237446 Yu Zhao 2022-09-18 4508 struct folio
*folio;
359a5e1416caaf Yu Zhao 2022-11-15 4509 struct folio
*next;
ac35a490237446 Yu Zhao 2022-09-18 4510 enum
vm_event_item item;
ac35a490237446 Yu Zhao 2022-09-18 4511 struct
reclaim_stat stat;
bd74fdaea14602 Yu Zhao 2022-09-18 4512 struct
lru_gen_mm_walk *walk;
359a5e1416caaf Yu Zhao 2022-11-15 4513 bool skip_retry
= false;
ac35a490237446 Yu Zhao 2022-09-18 4514 struct
mem_cgroup *memcg = lruvec_memcg(lruvec);
ac35a490237446 Yu Zhao 2022-09-18 4515 struct
pglist_data *pgdat = lruvec_pgdat(lruvec);
ac35a490237446 Yu Zhao 2022-09-18 4516
ac35a490237446 Yu Zhao 2022-09-18 4517
spin_lock_irq(>lru_lock);
ac35a490237446 Yu Zhao 2022-09-18 4518
ac35a490237446 Yu Zhao 2022-09-18 4519 scanned =
isolate_folios(lruvec, sc, swappiness, , );
ac35a490237446 Yu Zhao 2022-09-18 4520
ac35a490237446 Yu Zhao 2022-09-18 4521 scanned +=
try_to_inc_min_seq(lruvec, swappiness);
ac35a490237446 Yu Zhao 2022-09-18 4522
ac35a490237446 Yu Zhao 2022-09-18 4523 if
(get_nr_gens(lruvec, !swappiness) == MIN_NR_GENS)
ac35a490237446 Yu Zhao 2022-09-18 4524 scanned
= 0;
ac35a490237446 Yu Zhao 2022-09-18 4525
ac35a490237446 Yu Zhao 2022-09-18 4526
spin_unlock_irq(>lru_lock);
ac35a490237446 Yu Zhao 2022-09-18 4527
ac35a490237446 Yu Zhao 2022-09-18 4528 if
(list_empty())
ac35a490237446 Yu Zhao 2022-09-18 4529 return
scanned;
359a5e1416caaf Yu Zhao 2022-11-15 4530 retry:
49fd9b6df54e61 Matthew
Re: [PATCH -next 2/2] mm: vmscan: add new event to trace shrink lru
Hi Bixuan,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20231211]
url:
https://github.com/intel-lab-lkp/linux/commits/Bixuan-Cui/mm-shrinker-add-new-event-to-trace-shrink-count/20231212-112824
base: next-20231211
patch link:
https://lore.kernel.org/r/20231212032640.6968-3-cuibixuan%40vivo.com
patch subject: [PATCH -next 2/2] mm: vmscan: add new event to trace shrink lru
config: i386-buildonly-randconfig-003-20231214
(https://download.01.org/0day-ci/archive/20231214/202312142212.vbse7cms-...@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231214/202312142212.vbse7cms-...@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/202312142212.vbse7cms-...@intel.com/
All errors (new ones prefixed by >>):
mm/vmscan.c: In function 'evict_folios':
>> mm/vmscan.c:4533:9: error: implicit declaration of function
>> 'trace_mm_vmscan_lru_shrink_inactive'; did you mean
>> 'trace_mm_vmscan_lru_shrink_inactive_end'?
>> [-Werror=implicit-function-declaration]
4533 | trace_mm_vmscan_lru_shrink_inactive(pgdat->node_id,
| ^~~
| trace_mm_vmscan_lru_shrink_inactive_end
cc1: some warnings being treated as errors
vim +4533 mm/vmscan.c
ac35a490237446 Yu Zhao 2022-09-18 4500
a579086c99ed70 Yu Zhao 2022-12-21 4501 static int
evict_folios(struct lruvec *lruvec, struct scan_control *sc, int swappiness)
ac35a490237446 Yu Zhao 2022-09-18 4502 {
ac35a490237446 Yu Zhao 2022-09-18 4503 int type;
ac35a490237446 Yu Zhao 2022-09-18 4504 int scanned;
ac35a490237446 Yu Zhao 2022-09-18 4505 int reclaimed;
ac35a490237446 Yu Zhao 2022-09-18 4506 LIST_HEAD(list);
359a5e1416caaf Yu Zhao 2022-11-15 4507
LIST_HEAD(clean);
ac35a490237446 Yu Zhao 2022-09-18 4508 struct folio
*folio;
359a5e1416caaf Yu Zhao 2022-11-15 4509 struct folio
*next;
ac35a490237446 Yu Zhao 2022-09-18 4510 enum
vm_event_item item;
ac35a490237446 Yu Zhao 2022-09-18 4511 struct
reclaim_stat stat;
bd74fdaea14602 Yu Zhao 2022-09-18 4512 struct
lru_gen_mm_walk *walk;
359a5e1416caaf Yu Zhao 2022-11-15 4513 bool skip_retry
= false;
ac35a490237446 Yu Zhao 2022-09-18 4514 struct
mem_cgroup *memcg = lruvec_memcg(lruvec);
ac35a490237446 Yu Zhao 2022-09-18 4515 struct
pglist_data *pgdat = lruvec_pgdat(lruvec);
ac35a490237446 Yu Zhao 2022-09-18 4516
ac35a490237446 Yu Zhao 2022-09-18 4517
spin_lock_irq(>lru_lock);
ac35a490237446 Yu Zhao 2022-09-18 4518
ac35a490237446 Yu Zhao 2022-09-18 4519 scanned =
isolate_folios(lruvec, sc, swappiness, , );
ac35a490237446 Yu Zhao 2022-09-18 4520
ac35a490237446 Yu Zhao 2022-09-18 4521 scanned +=
try_to_inc_min_seq(lruvec, swappiness);
ac35a490237446 Yu Zhao 2022-09-18 4522
ac35a490237446 Yu Zhao 2022-09-18 4523 if
(get_nr_gens(lruvec, !swappiness) == MIN_NR_GENS)
ac35a490237446 Yu Zhao 2022-09-18 4524 scanned
= 0;
ac35a490237446 Yu Zhao 2022-09-18 4525
ac35a490237446 Yu Zhao 2022-09-18 4526
spin_unlock_irq(>lru_lock);
ac35a490237446 Yu Zhao 2022-09-18 4527
ac35a490237446 Yu Zhao 2022-09-18 4528 if
(list_empty())
ac35a490237446 Yu Zhao 2022-09-18 4529 return
scanned;
359a5e1416caaf Yu Zhao 2022-11-15 4530 retry:
49fd9b6df54e61 Matthew Wilcox (Oracle 2022-09-02 4531)reclaimed =
shrink_folio_list(, pgdat, sc, , false);
359a5e1416caaf Yu Zhao 2022-11-15 4532
sc->nr_reclaimed += reclaimed;
8c2214fc9a470a Jaewon Kim 2023-10-03 @4533
trace_mm_vmscan_lru_shrink_inactive(pgdat->node_id,
8c2214fc9a470a Jaewon Kim 2023-10-03 4534
scanned, reclaimed, , sc->priority,
8c2214fc9a470a Jaewon Kim 2023-10-03 4535
type ? LRU_INACTIVE_FILE : LRU_INACTIVE_ANON);
359a5e1416caaf Yu Zhao 2022-11-15 4536
359a5e1416caaf Yu Zhao 2022-11-15 4537
list_for_each_entry_safe_reverse(folio, next, , lru) {
359a5e1
[linus:master] [ring] f458a14534: WARNING:at_kernel/trace/ring_buffer_benchmark.c:#ring_buffer_consumer
Hello,
kernel test robot noticed
"WARNING:at_kernel/trace/ring_buffer_benchmark.c:#ring_buffer_consumer" on:
commit: f458a1453424e03462b5bb539673c9a3cddda480 ("ring-buffer: Test last
update in 32bit version of __rb_time_read()")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 26aff849438cebcd05f1a647390c4aa700d5c0f1]
[test failed on linux-next/master abb240f7a2bd14567ab53e602db562bb683391e6]
in testcase: locktorture
version:
with following parameters:
runtime: 300s
test: cpuhotplug
compiler: clang-16
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+---+++
| |
b2dd797543 | f458a14534 |
+---+++
| WARNING:at_kernel/trace/ring_buffer_benchmark.c:#ring_buffer_consumer | 0
| 14 |
| EIP:ring_buffer_consumer | 0
| 14 |
+---+++
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-lkp/202312121655.f8f36552-oliver.s...@intel.com
[ 38.075826][ T45] [ cut here ]
[ 38.077859][ T45] WARNING: CPU: 1 PID: 45 at
kernel/trace/ring_buffer_benchmark.c:147 ring_buffer_consumer
(kernel/trace/ring_buffer_benchmark.c:147)
[ 38.080140][ T45] Modules linked in:
[ 38.080906][ T45] CPU: 1 PID: 45 Comm: rb_consumer Not tainted
6.7.0-rc2-00015-gf458a1453424 #9
[ 38.082662][ T45] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 38.084759][ T45] EIP: ring_buffer_consumer
(kernel/trace/ring_buffer_benchmark.c:147)
[ 38.085829][ T45] Code: 00 83 e0 1f 8d 04 85 04 00 00 00 80 3d e4 48 ac c2 00
0f 84 00 ff ff ff eb 7c 80 3d e4 48 ac c2 00 75 73 c6 05 e4 48 ac c2 01 <0f> 0b
e9 d5 fe ff ff 80 3d e4 48 ac c2 00 75 5c c6 05 e4 48 ac c2
All code
0: 00 83 e0 1f 8d 04 add%al,0x48d1fe0(%rbx)
6: 85 04 00test %eax,(%rax,%rax,1)
9: 00 00 add%al,(%rax)
b: 80 3d e4 48 ac c2 00cmpb $0x0,-0x3d53b71c(%rip)#
0xc2ac48f6
12: 0f 84 00 ff ff ff je 0xff18
18: eb 7c jmp0x96
1a: 80 3d e4 48 ac c2 00cmpb $0x0,-0x3d53b71c(%rip)#
0xc2ac4905
21: 75 73 jne0x96
23: c6 05 e4 48 ac c2 01movb $0x1,-0x3d53b71c(%rip)#
0xc2ac490e
2a:* 0f 0b ud2 <-- trapping instruction
2c: e9 d5 fe ff ff jmp0xff06
31: 80 3d e4 48 ac c2 00cmpb $0x0,-0x3d53b71c(%rip)#
0xc2ac491c
38: 75 5c jne0x96
3a: c6 .byte 0xc6
3b: 05 e4 48 ac c2 add$0xc2ac48e4,%eax
Code starting with the faulting instruction
===
0: 0f 0b ud2
2: e9 d5 fe ff ff jmp0xfedc
7: 80 3d e4 48 ac c2 00cmpb $0x0,-0x3d53b71c(%rip)#
0xc2ac48f2
e: 75 5c jne0x6c
10: c6 .byte 0xc6
11: 05 e4 48 ac c2 add$0xc2ac48e4,%eax
[ 38.089748][ T45] EAX: c4f1b094 EBX: ECX: c4f1b08c EDX: 0001
[ 38.091153][ T45] ESI: 0080 EDI: EBP: c0c03f60 ESP: c0c03f28
[ 38.092549][ T45] DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 EFLAGS:
00010246
[ 38.093938][ T45] CR0: 80050033 CR2: CR3: 023d CR4: 00040690
[ 38.095291][ T45] Call Trace:
[ 38.095913][ T45] ? show_regs (arch/x86/kernel/dumpstack.c:478)
[ 38.096866][ T45] ? ring_buffer_consumer
(kernel/trace/ring_buffer_benchmark.c:147)
[ 38.097962][ T45] ? __warn (kernel/panic.c:236 kernel/panic.c:677)
[ 38.098783][ T45] ? ring_buffer_consumer
(kernel/trace/ring_buffer_benchmark.c:147)
[ 38.099849][ T45] ? ring_buffer_consumer
(kernel/trace/ring_buffer_benchmark.c:147)
[ 38.100987][ T45] ? report_bug (lib/bug.c:199)
[ 38.101835][ T45] ? exc_overflow (arch/x86/kernel/traps.c:250)
[ 38.102705][ T45] ? handle_bug (arch/x86/kernel/traps.c:237)
[ 38.103537][ T45] ? exc_invalid_op (arch/x86/kernel/traps.c:258)
[ 38.104583][ T45] ? handle_exception (arch/x86/entry/entry_32.S:1049)
[ 38.105519][ T45] ? exc_overflow (arch/x86/kernel/traps.c:250)
[ 38.106381][ T45] ? ring_buffer_consumer
(kernel/trace/ring_buffer_
Re: [PATCH] ipvs: add a stateless type of service and a stateless Maglev hashing scheduler
Hi Lev,
kernel test robot noticed the following build warnings:
[auto build test WARNING on horms-ipvs-next/master]
[also build test WARNING on horms-ipvs/master linus/master v6.7-rc4
next-20231206]
[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/Lev-Pantiukhin/ipvs-add-a-stateless-type-of-service-and-a-stateless-Maglev-hashing-scheduler/20231204-232344
base: https://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs-next.git
master
patch link:
https://lore.kernel.org/r/20231204152020.472247-1-kndrvt%40yandex-team.ru
patch subject: [PATCH] ipvs: add a stateless type of service and a stateless
Maglev hashing scheduler
config: microblaze-randconfig-r123-20231206
(https://download.01.org/0day-ci/archive/20231206/202312061823.o99vpf15-...@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 13.2.0
reproduce:
(https://download.01.org/0day-ci/archive/20231206/202312061823.o99vpf15-...@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/202312061823.o99vpf15-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> net/netfilter/ipvs/ip_vs_ctl.c:972:42: sparse: sparse: restricted __be32
>> degrades to integer
net/netfilter/ipvs/ip_vs_ctl.c:972:60: sparse: sparse: restricted __be32
degrades to integer
net/netfilter/ipvs/ip_vs_ctl.c:976:48: sparse: sparse: restricted __be32
degrades to integer
net/netfilter/ipvs/ip_vs_ctl.c:976:70: sparse: sparse: restricted __be32
degrades to integer
>> net/netfilter/ipvs/ip_vs_ctl.c:976:30: sparse: sparse: incorrect type in
>> assignment (different base types) @@ expected restricted __be32
>> [usertype] diff @@ got unsigned int @@
net/netfilter/ipvs/ip_vs_ctl.c:976:30: sparse: expected restricted
__be32 [usertype] diff
net/netfilter/ipvs/ip_vs_ctl.c:976:30: sparse: got unsigned int
>> net/netfilter/ipvs/ip_vs_ctl.c:978:41: sparse: sparse: cast from restricted
>> __be32
net/netfilter/ipvs/ip_vs_ctl.c:1532:27: sparse: sparse: dereference of
noderef expression
vim +972 net/netfilter/ipvs/ip_vs_ctl.c
962
963 static int __ip_vs_mh_compare_dests(struct list_head *a, struct
list_head *b)
964 {
965 struct ip_vs_dest *dest_a = list_entry(a, struct ip_vs_dest,
n_list);
966 struct ip_vs_dest *dest_b = list_entry(b, struct ip_vs_dest,
n_list);
967 unsigned int i = 0;
968 __be32 diff;
969
970 switch (dest_a->af) {
971 case AF_INET:
> 972 return (int)(dest_a->addr.ip - dest_b->addr.ip);
973
974 case AF_INET6:
975 for (; i < ARRAY_SIZE(dest_a->addr.ip6); i++) {
> 976 diff = dest_a->addr.ip6[i] -
> dest_b->addr.ip6[i];
977 if (diff)
> 978 return (int)diff;
979 }
980 }
981
982 return 0;
983 }
984
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v3 5/5] input/touchscreen: imagis: add support for IST3032C
Hi Karel, kernel test robot noticed the following build warnings: [auto build test WARNING on dtor-input/next] [also build test WARNING on dtor-input/for-linus robh/for-next linus/master v6.7-rc4 next-20231205] [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/Karel-Balej/dt-bindings-input-touchscreen-Add-compatible-for-IST3038B/20231202-215030 base: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next patch link: https://lore.kernel.org/r/20231202125948.10345-6-karelb%40gimli.ms.mff.cuni.cz patch subject: [PATCH v3 5/5] input/touchscreen: imagis: add support for IST3032C config: hexagon-randconfig-r111-20231204 (https://download.01.org/0day-ci/archive/20231205/202312052257.8qd4ocid-...@intel.com/config) compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a) reproduce: (https://download.01.org/0day-ci/archive/20231205/202312052257.8qd4ocid-...@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/202312052257.8qd4ocid-...@intel.com/ All warnings (new ones prefixed by >>): In file included from drivers/input/touchscreen/imagis.c:5: In file included from include/linux/i2c.h:19: In file included from include/linux/regulator/consumer.h:35: In file included from include/linux/suspend.h:5: In file included from include/linux/swap.h:9: In file included from include/linux/memcontrol.h:13: In file included from include/linux/cgroup.h:26: In file included from include/linux/kernel_stat.h:9: In file included from include/linux/interrupt.h:11: In file included from include/linux/hardirq.h:11: In file included from ./arch/hexagon/include/generated/asm/hardirq.h:1: In file included from include/asm-generic/hardirq.h:17: In file included from include/linux/irq.h:20: In file included from include/linux/io.h:13: In file included from arch/hexagon/include/asm/io.h:334: include/asm-generic/io.h:547:31: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 547 | val = __raw_readb(PCI_IOBASE + addr); | ~~ ^ include/asm-generic/io.h:560:61: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 560 | val = __le16_to_cpu((__le16 __force)__raw_readw(PCI_IOBASE + addr)); | ~~ ^ include/uapi/linux/byteorder/little_endian.h:37:51: note: expanded from macro '__le16_to_cpu' 37 | #define __le16_to_cpu(x) ((__force __u16)(__le16)(x)) | ^ In file included from drivers/input/touchscreen/imagis.c:5: In file included from include/linux/i2c.h:19: In file included from include/linux/regulator/consumer.h:35: In file included from include/linux/suspend.h:5: In file included from include/linux/swap.h:9: In file included from include/linux/memcontrol.h:13: In file included from include/linux/cgroup.h:26: In file included from include/linux/kernel_stat.h:9: In file included from include/linux/interrupt.h:11: In file included from include/linux/hardirq.h:11: In file included from ./arch/hexagon/include/generated/asm/hardirq.h:1: In file included from include/asm-generic/hardirq.h:17: In file included from include/linux/irq.h:20: In file included from include/linux/io.h:13: In file included from arch/hexagon/include/asm/io.h:334: include/asm-generic/io.h:573:61: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 573 | val = __le32_to_cpu((__le32 __force)__raw_readl(PCI_IOBASE + addr)); | ~~ ^ include/uapi/linux/byteorder/little_endian.h:35:51: note: expanded from macro '__le32_to_cpu' 35 | #define __le32_to_cpu(x) ((__force __u32)(__le32)(x)) | ^ In file included from drivers/input/touchscreen/imagis.c:5: In file included from include/linux/i2c.h:19: In file included from include/linux/regulator/consumer.h:35: In file included from include/linux/suspend.h:5: In file included from include/linux/swap.h:9: In file included from include/linux/memcontrol.h:13: In file included from include/linux/cgroup.h:26: In file included from include/linux/kernel_stat.h:9: In file included from include/linux/interrupt.h:11: I
Re: [PATCH v3 3/5] input/touchscreen: imagis: Add support for Imagis IST3038B
Hi Karel, kernel test robot noticed the following build warnings: [auto build test WARNING on dtor-input/next] [also build test WARNING on dtor-input/for-linus robh/for-next linus/master v6.7-rc4 next-20231205] [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/Karel-Balej/dt-bindings-input-touchscreen-Add-compatible-for-IST3038B/20231202-215030 base: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next patch link: https://lore.kernel.org/r/20231202125948.10345-4-karelb%40gimli.ms.mff.cuni.cz patch subject: [PATCH v3 3/5] input/touchscreen: imagis: Add support for Imagis IST3038B config: hexagon-randconfig-r111-20231204 (https://download.01.org/0day-ci/archive/20231205/202312051823.19cxz3sz-...@intel.com/config) compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a) reproduce: (https://download.01.org/0day-ci/archive/20231205/202312051823.19cxz3sz-...@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/202312051823.19cxz3sz-...@intel.com/ All warnings (new ones prefixed by >>): In file included from drivers/input/touchscreen/imagis.c:5: In file included from include/linux/i2c.h:19: In file included from include/linux/regulator/consumer.h:35: In file included from include/linux/suspend.h:5: In file included from include/linux/swap.h:9: In file included from include/linux/memcontrol.h:13: In file included from include/linux/cgroup.h:26: In file included from include/linux/kernel_stat.h:9: In file included from include/linux/interrupt.h:11: In file included from include/linux/hardirq.h:11: In file included from ./arch/hexagon/include/generated/asm/hardirq.h:1: In file included from include/asm-generic/hardirq.h:17: In file included from include/linux/irq.h:20: In file included from include/linux/io.h:13: In file included from arch/hexagon/include/asm/io.h:334: include/asm-generic/io.h:547:31: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 547 | val = __raw_readb(PCI_IOBASE + addr); | ~~ ^ include/asm-generic/io.h:560:61: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 560 | val = __le16_to_cpu((__le16 __force)__raw_readw(PCI_IOBASE + addr)); | ~~ ^ include/uapi/linux/byteorder/little_endian.h:37:51: note: expanded from macro '__le16_to_cpu' 37 | #define __le16_to_cpu(x) ((__force __u16)(__le16)(x)) | ^ In file included from drivers/input/touchscreen/imagis.c:5: In file included from include/linux/i2c.h:19: In file included from include/linux/regulator/consumer.h:35: In file included from include/linux/suspend.h:5: In file included from include/linux/swap.h:9: In file included from include/linux/memcontrol.h:13: In file included from include/linux/cgroup.h:26: In file included from include/linux/kernel_stat.h:9: In file included from include/linux/interrupt.h:11: In file included from include/linux/hardirq.h:11: In file included from ./arch/hexagon/include/generated/asm/hardirq.h:1: In file included from include/asm-generic/hardirq.h:17: In file included from include/linux/irq.h:20: In file included from include/linux/io.h:13: In file included from arch/hexagon/include/asm/io.h:334: include/asm-generic/io.h:573:61: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 573 | val = __le32_to_cpu((__le32 __force)__raw_readl(PCI_IOBASE + addr)); | ~~ ^ include/uapi/linux/byteorder/little_endian.h:35:51: note: expanded from macro '__le32_to_cpu' 35 | #define __le32_to_cpu(x) ((__force __u32)(__le32)(x)) | ^ In file included from drivers/input/touchscreen/imagis.c:5: In file included from include/linux/i2c.h:19: In file included from include/linux/regulator/consumer.h:35: In file included from include/linux/suspend.h:5: In file included from include/linux/swap.h:9: In file included from include/linux/memcontrol.h:13: In file included from include/linux/cgroup.h:26: In file included from include/linux/kernel_stat.h:9: In file included from include/linux/interrup
[mhiramat:topic/fprobe-on-fgraph] [function_graph] 1c96d64aa1: WARNING:at_kernel/trace/trace.c:#run_tracer_selftest
Hello,
kernel test robot noticed
"WARNING:at_kernel/trace/trace.c:#run_tracer_selftest" on:
commit: 1c96d64aa1853ed6272439901bb8daa85b012d89 ("function_graph: Add a new
entry handler with parent_ip and ftrace_regs")
https://git.kernel.org/cgit/linux/kernel/git/mhiramat/linux.git
topic/fprobe-on-fgraph
in testcase: boot
compiler: gcc-12
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+--+++
|
| c9e840a68b | 1c96d64aa1 |
+--+++
| WARNING:at_kernel/trace/trace.c:#run_tracer_selftest
| 0 | 6 |
| EIP:run_tracer_selftest
| 0 | 6 |
+--+++
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-lkp/202311241731.d1159c9f-oliver.s...@intel.com
[ 10.938801][T1] [ cut here ]
[ 10.938801][ T1] WARNING: CPU: 1 PID: 1 at kernel/trace/trace.c:2030
run_tracer_selftest (kernel/trace/trace.c:2030)
[ 10.939915][T1] Modules linked in:
[ 10.940689][T1] CPU: 1 PID: 1 Comm: swapper/0 Not tainted
6.6.0-rc7-00021-g1c96d64aa185 #1
[ 10.945702][T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 10.947518][ T1] EIP: run_tracer_selftest (kernel/trace/trace.c:2030)
[ 10.948530][ T1] Code: 00 00 00 00 66 90 8b 15 ac 05 1d c3 a1 e8 05 1d c3 b9
ff ff ff ff e8 07 5c ff ff e9 29 fe ff ff 68 2f 0b be c2 e8 b4 8d f5 ff <0f> 0b
b8 ff ff ff ff 5a e9 a5 fe ff ff b8 f4 ff ff ff e9 9b fe ff
All code
0: 00 00 add%al,(%rax)
2: 00 00 add%al,(%rax)
4: 66 90 xchg %ax,%ax
6: 8b 15 ac 05 1d c3 mov-0x3ce2fa54(%rip),%edx#
0xc31d05b8
c: a1 e8 05 1d c3 b9 ffmovabs 0xffb9c31d05e8,%eax
13: ff ff
15: ff (bad)
16: e8 07 5c ff ff call 0x5c22
1b: e9 29 fe ff ff jmp0xfe49
20: 68 2f 0b be c2 push $0xc2be0b2f
25: e8 b4 8d f5 ff call 0xfff58dde
2a:* 0f 0b ud2 <-- trapping instruction
2c: b8 ff ff ff ff mov$0x,%eax
31: 5a pop%rdx
32: e9 a5 fe ff ff jmp0xfedc
37: b8 f4 ff ff ff mov$0xfff4,%eax
3c: e9 .byte 0xe9
3d: 9b fwait
3e: fe (bad)
3f: ff .byte 0xff
Code starting with the faulting instruction
===
0: 0f 0b ud2
2: b8 ff ff ff ff mov$0x,%eax
7: 5a pop%rdx
8: e9 a5 fe ff ff jmp0xfeb2
d: b8 f4 ff ff ff mov$0xfff4,%eax
12: e9 .byte 0xe9
13: 9b fwait
14: fe (bad)
15: ff .byte 0xff
[ 10.950058][T1] EAX: 0007 EBX: c345a6a0 ECX: EDX:
[ 10.951304][T1] ESI: c2be3ee0 EDI: c4434400 EBP: c4d97ee4 ESP: c4d97ed4
[ 10.952559][T1] DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 EFLAGS:
00010246
[ 10.953640][T1] CR0: 80050033 CR2: CR3: 03696000 CR4: 000406d0
[ 10.954878][T1] DR0: DR1: DR2: DR3:
[ 10.956215][T1] DR6: fffe0ff0 DR7: 0400
[ 10.957111][T1] Call Trace:
[ 10.957426][ T1] ? show_regs (arch/x86/kernel/dumpstack.c:479
arch/x86/kernel/dumpstack.c:465)
[ 10.958254][ T1] ? run_tracer_selftest (kernel/trace/trace.c:2030)
[ 10.959206][ T1] ? __warn (kernel/panic.c:673)
[ 10.960018][ T1] ? run_tracer_selftest (kernel/trace/trace.c:2030)
[ 10.960992][ T1] ? report_bug (lib/bug.c:201 lib/bug.c:219)
[ 10.961462][ T1] ? exc_overflow (arch/x86/kernel/traps.c:250)
[ 10.962321][ T1] ? handle_bug (arch/x86/kernel/traps.c:216)
[ 10.963166][ T1] ? exc_invalid_op (arch/x86/kernel/traps.c:258 (discriminator
1))
[ 10.964052][ T1] ? handle_exception (arch/x86/entry/entry_32.S:1056)
[ 10.965001][ T1] ? exc_overflow (arch/x86/kernel/traps.c:250)
[ 10.965461][ T1] ? run_tracer_selftest (kernel/trace/trace.c:2030)
[ 10.966444][ T1] ?
Re: [PATCH] rethook: Use __rcu pointer for rethook::handler
Hi Masami,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.7-rc2 next-20231124]
[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/Masami-Hiramatsu-Google/rethook-Use-__rcu-pointer-for-rethook-handler/20231124-090634
base: linus/master
patch link:
https://lore.kernel.org/r/170078778632.209874.7893551840863388753.stgit%40devnote2
patch subject: [PATCH] rethook: Use __rcu pointer for rethook::handler
config: x86_64-randconfig-r113-20231124
(https://download.01.org/0day-ci/archive/20231124/202311241808.rv9ceuah-...@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git
ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231124/202311241808.rv9ceuah-...@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/202311241808.rv9ceuah-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/trace/rethook.c:51:9: sparse: sparse: incompatible types in
>> comparison expression (different address spaces):
>> kernel/trace/rethook.c:51:9: sparse:void ( [noderef] __rcu * )( ... )
>> kernel/trace/rethook.c:51:9: sparse:void ( * )( ... )
kernel/trace/rethook.c:66:9: sparse: sparse: incompatible types in
comparison expression (different address spaces):
kernel/trace/rethook.c:66:9: sparse:void ( [noderef] __rcu * )( ... )
kernel/trace/rethook.c:66:9: sparse:void ( * )( ... )
kernel/trace/rethook.c:110:9: sparse: sparse: incompatible types in
comparison expression (different address spaces):
kernel/trace/rethook.c:110:9: sparse:void ( [noderef] __rcu * )( ... )
kernel/trace/rethook.c:110:9: sparse:void ( * )( ... )
kernel/trace/rethook.c:140:19: sparse: sparse: incompatible types in
comparison expression (different address spaces):
kernel/trace/rethook.c:140:19: sparse:void ( [noderef] __rcu * )( ... )
kernel/trace/rethook.c:140:19: sparse:void ( * )( ... )
kernel/trace/rethook.c:161:19: sparse: sparse: incompatible types in
comparison expression (different address spaces):
kernel/trace/rethook.c:161:19: sparse:void ( [noderef] __rcu * )( ... )
kernel/trace/rethook.c:161:19: sparse:void ( * )( ... )
kernel/trace/rethook.c:305:27: sparse: sparse: incompatible types in
comparison expression (different address spaces):
kernel/trace/rethook.c:305:27: sparse:void ( [noderef] __rcu * )( ... )
kernel/trace/rethook.c:305:27: sparse:void ( * )( ... )
vim +51 kernel/trace/rethook.c
40
41 /**
42 * rethook_stop() - Stop using a rethook.
43 * @rh: the struct rethook to stop.
44 *
45 * Stop using a rethook to prepare for freeing it. If you want to wait
for
46 * all running rethook handler before calling rethook_free(), you need
to
47 * call this first and wait RCU, and call rethook_free().
48 */
49 void rethook_stop(struct rethook *rh)
50 {
> 51 rcu_assign_pointer(rh->handler, NULL);
52 }
53
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2 3/5] modpost: Extended modversion support
Hi Matthew, kernel test robot noticed the following build errors: [auto build test ERROR on mcgrof/modules-next] [also build test ERROR on powerpc/next powerpc/fixes masahiroy-kbuild/for-next masahiroy-kbuild/fixes linus/master v6.7-rc1 next-20231117] [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/Matthew-Maurer/export_report-Rehabilitate-script/20231118-110040 base: https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git modules-next patch link: https://lore.kernel.org/r/20231118025748.2778044-4-mmaurer%40google.com patch subject: [PATCH v2 3/5] modpost: Extended modversion support config: powerpc-allmodconfig (https://download.01.org/0day-ci/archive/20231118/202311182118.zjqkg301-...@intel.com/config) compiler: powerpc64-linux-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231118/202311182118.zjqkg301-...@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/202311182118.zjqkg301-...@intel.com/ All errors (new ones prefixed by >>): >> arch/powerpc/kernel/module_64.c:25:10: fatal error: string.h: No such file >> or directory 25 | #include | ^~ compilation terminated. vim +25 arch/powerpc/kernel/module_64.c 8 9 #include 10 #include 11 #include 12 #include 13 #include 14 #include 15 #include 16 #include 17 #include 18 #include 19 #include 20 #include 21 #include 22 #include 23 #include 24 #include > 25 #include 26 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH 27/32] s390/string: Add KMSAN support
Hi Ilya, kernel test robot noticed the following build errors: [auto build test ERROR on s390/features] [also build test ERROR on akpm-mm/mm-everything linus/master vbabka-slab/for-next v6.7-rc1 next-20231116] [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/Ilya-Leoshkevich/ftrace-Unpoison-ftrace_regs-in-ftrace_ops_list_func/20231116-045608 base: https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git features patch link: https://lore.kernel.org/r/20231115203401.2495875-28-iii%40linux.ibm.com patch subject: [PATCH 27/32] s390/string: Add KMSAN support config: s390-debug_defconfig (https://download.01.org/0day-ci/archive/20231117/202311170550.bsbo44ix-...@intel.com/config) compiler: s390-linux-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231117/202311170550.bsbo44ix-...@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/202311170550.bsbo44ix-...@intel.com/ All errors (new ones prefixed by >>): s390-linux-ld: arch/s390/mm/vmem.o: in function `crst_table_init': >> arch/s390/include/asm/pgalloc.h:33:(.text+0x1ba): undefined reference to >> `memset64' s390-linux-ld: arch/s390/mm/vmem.o: in function `vmem_pte_alloc': >> arch/s390/mm/vmem.c:68:(.ref.text+0x1ec): undefined reference to `memset64' s390-linux-ld: arch/s390/mm/pgalloc.o: in function `base_pgt_alloc': >> arch/s390/mm/pgalloc.c:241:(.text+0x184): undefined reference to `memset64' s390-linux-ld: arch/s390/mm/pgalloc.o: in function `crst_table_init': arch/s390/include/asm/pgalloc.h:33:(.text+0x3e8): undefined reference to `memset64' >> s390-linux-ld: arch/s390/include/asm/pgalloc.h:33:(.text+0x568): undefined >> reference to `memset64' s390-linux-ld: arch/s390/mm/pgalloc.o:arch/s390/include/asm/pgalloc.h:33: more undefined references to `memset64' follow s390-linux-ld: lib/test_string.o: in function `memset16_selftest': >> lib/test_string.c:19:(.init.text+0x94): undefined reference to `memset16' s390-linux-ld: lib/test_string.o: in function `memset32_selftest': >> lib/test_string.c:55:(.init.text+0x234): undefined reference to `memset32' s390-linux-ld: lib/test_string.o: in function `memset64_selftest': >> lib/test_string.c:91:(.init.text+0x3c2): undefined reference to `memset64' s390-linux-ld: drivers/video/fbdev/core/fbcon.o: in function `scr_memsetw': >> include/linux/vt_buffer.h:36:(.text+0x30f6): undefined reference to >> `memset16' >> s390-linux-ld: include/linux/vt_buffer.h:36:(.text+0x320a): undefined >> reference to `memset16' s390-linux-ld: include/linux/vt_buffer.h:36:(.text+0x32c4): undefined reference to `memset16' s390-linux-ld: include/linux/vt_buffer.h:36:(.text+0x33b8): undefined reference to `memset16' s390-linux-ld: include/linux/vt_buffer.h:36:(.text+0x4f60): undefined reference to `memset16' s390-linux-ld: drivers/video/fbdev/core/fbcon.o:include/linux/vt_buffer.h:36: more undefined references to `memset16' follow s390-linux-ld: drivers/tty/vt/vt.o: in function `vc_uniscr_copy_area': >> drivers/tty/vt/vt.c:464:(.text+0x107e): undefined reference to `memset32' >> s390-linux-ld: drivers/tty/vt/vt.c:471:(.text+0x1104): undefined reference >> to `memset32' s390-linux-ld: drivers/tty/vt/vt.c:471:(.text+0x1118): undefined reference to `memset32' s390-linux-ld: drivers/tty/vt/vt.c:471:(.text+0x1140): undefined reference to `memset32' s390-linux-ld: drivers/tty/vt/vt.o: in function `vc_uniscr_insert': drivers/tty/vt/vt.c:374:(.text+0x13a4): undefined reference to `memset32' s390-linux-ld: drivers/tty/vt/vt.o:drivers/tty/vt/vt.c:385: more undefined references to `memset32' follow s390-linux-ld: drivers/tty/vt/vt.o: in function `scr_memsetw': include/linux/vt_buffer.h:36:(.text+0x2844): undefined reference to `memset16' s390-linux-ld: include/linux/vt_buffer.h:36:(.text+0x2932): undefined reference to `memset16' s390-linux-ld: include/linux/vt_buffer.h:36:(.text+0x2fe8): undefined reference to `memset16' s390-linux-ld: include/linux/vt_buffer.h:36:(.text+0x319c): undefined reference to `memset16' s390-linux-ld: drivers/tty/vt/vt.o: in function `vc_uniscr_clear_line': drivers/tty/vt/vt.c:393:(.text+0x3f78): undefined reference to `memset32' s390-linux-ld: drivers/tty/vt/vt.o: in function `vc_uniscr_clear_lines': drivers/tty/vt/vt.c:401:(.text+0x3fb8): undefined reference to `memset32' s390-linux-ld: drivers/tty/vt/vt.c:401:(.text+0x3fe2): undefined reference to `memset32'
Re: [PATCH] input: touchscreen: imagis: Add touch key support
Hi Duje,
kernel test robot noticed the following build errors:
[auto build test ERROR on dtor-input/next]
[also build test ERROR on dtor-input/for-linus linus/master v6.6 next-20231110]
[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/Duje-Mihanovi/input-touchscreen-imagis-Add-touch-key-support/20231113-034453
base: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
patch link:
https://lore.kernel.org/r/20231112194124.24916-1-duje.mihanovic%40skole.hr
patch subject: [PATCH] input: touchscreen: imagis: Add touch key support
config: m68k-allmodconfig
(https://download.01.org/0day-ci/archive/20231113/202311130533.estbdamt-...@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231113/202311130533.estbdamt-...@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/r/202311130533.estbdamt-...@intel.com/
All errors (new ones prefixed by >>):
drivers/input/touchscreen/imagis.c: In function 'imagis_interrupt':
>> drivers/input/touchscreen/imagis.c:149:23: error: implicit declaration of
>> function 'FIELD_GET' [-Werror=implicit-function-declaration]
149 | key_pressed = FIELD_GET(IST3032C_KEY_STATUS_MASK,
intr_message);
| ^
cc1: some warnings being treated as errors
vim +/FIELD_GET +149 drivers/input/touchscreen/imagis.c
a23ba3c043db9a Markuss Broks 2022-03-14 95
a23ba3c043db9a Markuss Broks 2022-03-14 96 static irqreturn_t
imagis_interrupt(int irq, void *dev_id)
a23ba3c043db9a Markuss Broks 2022-03-14 97 {
a23ba3c043db9a Markuss Broks 2022-03-14 98 struct imagis_ts *ts = dev_id;
a23ba3c043db9a Markuss Broks 2022-03-14 99 u32 intr_message, finger_status;
7371770ece2db7 Duje Mihanović 2023-11-12 100 unsigned int finger_count,
finger_pressed, key_pressed;
a23ba3c043db9a Markuss Broks 2022-03-14 101 int i;
a23ba3c043db9a Markuss Broks 2022-03-14 102 int error;
a23ba3c043db9a Markuss Broks 2022-03-14 103
8eb834ae8a9b34 Markuss Broks 2023-10-03 104 error = imagis_i2c_read_reg(ts,
ts->tdata->interrupt_msg_cmd, _message);
a23ba3c043db9a Markuss Broks 2022-03-14 105 if (error) {
a23ba3c043db9a Markuss Broks 2022-03-14 106
dev_err(>client->dev,
a23ba3c043db9a Markuss Broks 2022-03-14 107 "failed to read
the interrupt message: %d\n", error);
a23ba3c043db9a Markuss Broks 2022-03-14 108 goto out;
a23ba3c043db9a Markuss Broks 2022-03-14 109 }
a23ba3c043db9a Markuss Broks 2022-03-14 110
a23ba3c043db9a Markuss Broks 2022-03-14 111 finger_count = (intr_message &
IST3038C_FINGER_COUNT_MASK) >>
a23ba3c043db9a Markuss Broks 2022-03-14 112
IST3038C_FINGER_COUNT_SHIFT;
a23ba3c043db9a Markuss Broks 2022-03-14 113 if (finger_count >
IST3038C_MAX_FINGER_NUM) {
a23ba3c043db9a Markuss Broks 2022-03-14 114
dev_err(>client->dev,
a23ba3c043db9a Markuss Broks 2022-03-14 115 "finger count
%d is more than maximum supported\n",
a23ba3c043db9a Markuss Broks 2022-03-14 116 finger_count);
a23ba3c043db9a Markuss Broks 2022-03-14 117 goto out;
a23ba3c043db9a Markuss Broks 2022-03-14 118 }
a23ba3c043db9a Markuss Broks 2022-03-14 119
a23ba3c043db9a Markuss Broks 2022-03-14 120 finger_pressed = intr_message &
IST3038C_FINGER_STATUS_MASK;
a23ba3c043db9a Markuss Broks 2022-03-14 121
a23ba3c043db9a Markuss Broks 2022-03-14 122 for (i = 0; i < finger_count;
i++) {
8eb834ae8a9b34 Markuss Broks 2023-10-03 123 if
(ts->tdata->protocol_b)
a23ba3c043db9a Markuss Broks 2022-03-14 124 error =
imagis_i2c_read_reg(ts,
8eb834ae8a9b34 Markuss Broks 2023-10-03 125
ts->tdata->touch_coord_cmd, _status);
8eb834ae8a9b34 Markuss Broks 2023-10-03 126 else
8eb834ae8a9b34 Markuss Broks 2023-10-03 127 error =
imagis_i2c_read_reg(ts,
8eb834ae8a9b34 Markuss Broks 2023-10-03 128
ts->tdata->touch_coord_cmd + (i * 4),
a23ba3c043db9a Markuss Broks 2022-03-14 129
_status);
a23ba3c043db9a Markuss Broks 2022-03-14 130 if (error) {
a23ba3c043db9a Markuss Broks 2022-03-14 131
dev_err(>client->dev,
a23ba3c043db9a Markuss Broks 2022-03-14 132
Re: [PATCH v4] bus: mhi: host: Add tracing support
Hi Krishna, kernel test robot noticed the following build warnings: [auto build test WARNING on 3006adf3be79cde4d14b1800b963b82b6e5572e0] url: https://github.com/intel-lab-lkp/linux/commits/Krishna-chaitanya-chundru/bus-mhi-host-Add-tracing-support/2023-135816 base: 3006adf3be79cde4d14b1800b963b82b6e5572e0 patch link: https://lore.kernel.org/r/2023-ftrace_support-v4-1-c83602399461%40quicinc.com patch subject: [PATCH v4] bus: mhi: host: Add tracing support config: i386-randconfig-062-2023 (https://download.01.org/0day-ci/archive/20231112/202311120247.semdyrt6-...@intel.com/config) compiler: gcc-11 (Debian 11.3.0-12) 11.3.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231112/202311120247.semdyrt6-...@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/202311120247.semdyrt6-...@intel.com/ sparse warnings: (new ones prefixed by >>) drivers/bus/mhi/host/init.c: note: in included file (through include/trace/trace_events.h, include/trace/define_trace.h, drivers/bus/mhi/host/trace.h): drivers/bus/mhi/host/./trace.h:17:1: sparse: sparse: cast to restricted __le64 drivers/bus/mhi/host/./trace.h:17:1: sparse: sparse: restricted __le64 degrades to integer drivers/bus/mhi/host/./trace.h:17:1: sparse: sparse: restricted __le64 degrades to integer drivers/bus/mhi/host/./trace.h:17:1: sparse: sparse: cast to restricted __le32 drivers/bus/mhi/host/./trace.h:17:1: sparse: sparse: restricted __le32 degrades to integer drivers/bus/mhi/host/./trace.h:17:1: sparse: sparse: restricted __le32 degrades to integer drivers/bus/mhi/host/./trace.h:17:1: sparse: sparse: cast to restricted __le32 drivers/bus/mhi/host/./trace.h:17:1: sparse: sparse: restricted __le32 degrades to integer drivers/bus/mhi/host/./trace.h:17:1: sparse: sparse: restricted __le32 degrades to integer drivers/bus/mhi/host/./trace.h:99:1: sparse: sparse: cast to restricted __le64 drivers/bus/mhi/host/./trace.h:99:1: sparse: sparse: restricted __le64 degrades to integer drivers/bus/mhi/host/./trace.h:99:1: sparse: sparse: restricted __le64 degrades to integer drivers/bus/mhi/host/./trace.h:99:1: sparse: sparse: cast to restricted __le32 drivers/bus/mhi/host/./trace.h:99:1: sparse: sparse: restricted __le32 degrades to integer drivers/bus/mhi/host/./trace.h:99:1: sparse: sparse: restricted __le32 degrades to integer drivers/bus/mhi/host/./trace.h:99:1: sparse: sparse: cast to restricted __le32 drivers/bus/mhi/host/./trace.h:99:1: sparse: sparse: restricted __le32 degrades to integer drivers/bus/mhi/host/./trace.h:99:1: sparse: sparse: restricted __le32 degrades to integer drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: cast to restricted __le64 drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: restricted __le64 degrades to integer drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: restricted __le64 degrades to integer drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: cast to restricted __le32 drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: restricted __le32 degrades to integer drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: restricted __le32 degrades to integer drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: cast to restricted __le32 drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: restricted __le32 degrades to integer drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: restricted __le32 degrades to integer drivers/bus/mhi/host/init.c: note: in included file (through include/trace/trace_events.h, include/trace/define_trace.h, drivers/bus/mhi/host/trace.h): >> drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: non size-preserving >> pointer to integer cast drivers/bus/mhi/host/init.c: note: in included file (through include/trace/perf.h, include/trace/define_trace.h, drivers/bus/mhi/host/trace.h): >> drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: non size-preserving >> pointer to integer cast vim +123 drivers/bus/mhi/host/./trace.h 122 > 123 TRACE_EVENT(mhi_process_ctrl_ev_ring, 124 125 TP_PROTO(const char *name, struct mhi_ring_element *rp, __le64 ptr, 126 __le32 dword0, __le32 dword1), 127 128 TP_ARGS(name, rp, ptr, dword0, dword1), 129 130 TP_STRUCT__entry( 131 __field(u64, rp) 132 __field(__le64, ptr) 133 __string(name, name) 134 __field(__le32, dword0) 135 __field(__le32, dword1) 136 __field(int, state) 137 ), 138 139 TP_fast_assign( 140 __assign_str(name, name);
Re: [PATCH v4] bus: mhi: host: Add tracing support
Hi Krishna,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 3006adf3be79cde4d14b1800b963b82b6e5572e0]
url:
https://github.com/intel-lab-lkp/linux/commits/Krishna-chaitanya-chundru/bus-mhi-host-Add-tracing-support/2023-135816
base: 3006adf3be79cde4d14b1800b963b82b6e5572e0
patch link:
https://lore.kernel.org/r/2023-ftrace_support-v4-1-c83602399461%40quicinc.com
patch subject: [PATCH v4] bus: mhi: host: Add tracing support
config: x86_64-randconfig-123-2023
(https://download.01.org/0day-ci/archive/2023/20232133.5qrqkz0r-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/2023/20232133.5qrqkz0r-...@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/20232133.5qrqkz0r-...@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/bus/mhi/host/init.c: note: in included file (through
include/trace/trace_events.h, include/trace/define_trace.h,
drivers/bus/mhi/host/trace.h):
>> drivers/bus/mhi/host/./trace.h:17:1: sparse: sparse: cast to restricted
>> __le64
>> drivers/bus/mhi/host/./trace.h:17:1: sparse: sparse: restricted __le64
>> degrades to integer
>> drivers/bus/mhi/host/./trace.h:17:1: sparse: sparse: restricted __le64
>> degrades to integer
>> drivers/bus/mhi/host/./trace.h:17:1: sparse: sparse: cast to restricted
>> __le32
>> drivers/bus/mhi/host/./trace.h:17:1: sparse: sparse: restricted __le32
>> degrades to integer
>> drivers/bus/mhi/host/./trace.h:17:1: sparse: sparse: restricted __le32
>> degrades to integer
>> drivers/bus/mhi/host/./trace.h:17:1: sparse: sparse: cast to restricted
>> __le32
>> drivers/bus/mhi/host/./trace.h:17:1: sparse: sparse: restricted __le32
>> degrades to integer
>> drivers/bus/mhi/host/./trace.h:17:1: sparse: sparse: restricted __le32
>> degrades to integer
drivers/bus/mhi/host/./trace.h:99:1: sparse: sparse: cast to restricted
__le64
drivers/bus/mhi/host/./trace.h:99:1: sparse: sparse: restricted __le64
degrades to integer
drivers/bus/mhi/host/./trace.h:99:1: sparse: sparse: restricted __le64
degrades to integer
drivers/bus/mhi/host/./trace.h:99:1: sparse: sparse: cast to restricted
__le32
drivers/bus/mhi/host/./trace.h:99:1: sparse: sparse: restricted __le32
degrades to integer
drivers/bus/mhi/host/./trace.h:99:1: sparse: sparse: restricted __le32
degrades to integer
drivers/bus/mhi/host/./trace.h:99:1: sparse: sparse: cast to restricted
__le32
drivers/bus/mhi/host/./trace.h:99:1: sparse: sparse: restricted __le32
degrades to integer
drivers/bus/mhi/host/./trace.h:99:1: sparse: sparse: restricted __le32
degrades to integer
drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: cast to restricted
__le64
drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: restricted __le64
degrades to integer
drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: restricted __le64
degrades to integer
drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: cast to restricted
__le32
drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: restricted __le32
degrades to integer
drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: restricted __le32
degrades to integer
drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: cast to restricted
__le32
drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: restricted __le32
degrades to integer
drivers/bus/mhi/host/./trace.h:123:1: sparse: sparse: restricted __le32
degrades to integer
vim +17 drivers/bus/mhi/host/./trace.h
16
> 17 TRACE_EVENT(mhi_gen_tre,
18
19 TP_PROTO(const char *name, int ch_num, u64 wp, __le64 tre_ptr,
20 __le32 dword0, __le32 dword1),
21
22 TP_ARGS(name, ch_num, wp, tre_ptr, dword0, dword1),
23
24 TP_STRUCT__entry(
25 __string(name, name)
26 __field(int, ch_num)
27 __field(u64, wp)
28 __field(__le64, tre_ptr)
29 __field(__le32, dword0)
30 __field(__le32, dword1)
31 ),
32
33 TP_fast_assign(
34 __assign_str(name, name);
35 __entry->ch_num = ch_num;
36 __entry->wp = wp;
37 __entry->tre_ptr = tre_ptr;
38 __entry->dword0 = dword0;
39 __entry->dword1 = dword1;
40 ),
41
42 TP_printk("%s: Chan: %d WP: 0x%llx TRE: 0x%llx 0x%08x 0x%08x\n",
43__get_str(
Re: [PATCH v4] bus: mhi: host: Add tracing support
Hi Krishna,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 3006adf3be79cde4d14b1800b963b82b6e5572e0]
url:
https://github.com/intel-lab-lkp/linux/commits/Krishna-chaitanya-chundru/bus-mhi-host-Add-tracing-support/2023-135816
base: 3006adf3be79cde4d14b1800b963b82b6e5572e0
patch link:
https://lore.kernel.org/r/2023-ftrace_support-v4-1-c83602399461%40quicinc.com
patch subject: [PATCH v4] bus: mhi: host: Add tracing support
config: csky-randconfig-002-2023
(https://download.01.org/0day-ci/archive/2023/20231502.weci1okb-...@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/2023/20231502.weci1okb-...@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/20231502.weci1okb-...@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/trace/define_trace.h:102,
from drivers/bus/mhi/host/trace.h:225,
from drivers/bus/mhi/host/init.c:24:
drivers/bus/mhi/host/./trace.h: In function
'trace_event_raw_event_mhi_process_ctrl_ev_ring':
>> drivers/bus/mhi/host/./trace.h:141:31: warning: cast from pointer to integer
>> of different size [-Wpointer-to-int-cast]
141 | __entry->rp = (u64)rp;
| ^
include/trace/trace_events.h:402:11: note: in definition of macro
'DECLARE_EVENT_CLASS'
402 | { assign; }
\
| ^~
include/trace/trace_events.h:44:30: note: in expansion of macro 'PARAMS'
44 | PARAMS(assign), \
| ^~
drivers/bus/mhi/host/./trace.h:123:1: note: in expansion of macro
'TRACE_EVENT'
123 | TRACE_EVENT(mhi_process_ctrl_ev_ring,
| ^~~
drivers/bus/mhi/host/./trace.h:139:9: note: in expansion of macro
'TP_fast_assign'
139 | TP_fast_assign(
| ^~
In file included from include/trace/define_trace.h:103:
drivers/bus/mhi/host/./trace.h: In function
'perf_trace_mhi_process_ctrl_ev_ring':
>> drivers/bus/mhi/host/./trace.h:141:31: warning: cast from pointer to integer
>> of different size [-Wpointer-to-int-cast]
141 | __entry->rp = (u64)rp;
| ^
include/trace/perf.h:51:11: note: in definition of macro
'DECLARE_EVENT_CLASS'
51 | { assign; }
\
| ^~
include/trace/trace_events.h:44:30: note: in expansion of macro 'PARAMS'
44 | PARAMS(assign), \
| ^~
drivers/bus/mhi/host/./trace.h:123:1: note: in expansion of macro
'TRACE_EVENT'
123 | TRACE_EVENT(mhi_process_ctrl_ev_ring,
| ^~~
drivers/bus/mhi/host/./trace.h:139:9: note: in expansion of macro
'TP_fast_assign'
139 | TP_fast_assign(
| ^~
vim +141 drivers/bus/mhi/host/./trace.h
124
125 TP_PROTO(const char *name, struct mhi_ring_element *rp, __le64
ptr,
126 __le32 dword0, __le32 dword1),
127
128 TP_ARGS(name, rp, ptr, dword0, dword1),
129
130 TP_STRUCT__entry(
131 __field(u64, rp)
132 __field(__le64, ptr)
133 __string(name, name)
134 __field(__le32, dword0)
135 __field(__le32, dword1)
136 __field(int, state)
137 ),
138
139 TP_fast_assign(
140 __assign_str(name, name);
> 141 __entry->rp = (u64)rp;
142 __entry->ptr = ptr;
143 __entry->dword0 = dword0;
144 __entry->dword1 = dword1;
145 __entry->state = MHI_TRE_GET_EV_STATE(rp);
146 ),
147
148 TP_printk("%s: RP:0x%llx Processing Event:0x%llx 0x%08x 0x%08x
state:%s\n",
149__get_str(name), __entry->rp, __entry->ptr,
__entry->dword0,
150__entry->dword1, mhi_state_str(__entry->state))
151 );
152
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v3] bus: mhi: host: Add tracing support
Hi Krishna,
kernel test robot noticed the following build errors:
[auto build test ERROR on 3006adf3be79cde4d14b1800b963b82b6e5572e0]
url:
https://github.com/intel-lab-lkp/linux/commits/Krishna-chaitanya-chundru/bus-mhi-host-Add-tracing-support/2023-101955
base: 3006adf3be79cde4d14b1800b963b82b6e5572e0
patch link:
https://lore.kernel.org/r/2023-ftrace_support-v3-1-f358d2911a74%40quicinc.com
patch subject: [PATCH v3] bus: mhi: host: Add tracing support
config: sh-allmodconfig
(https://download.01.org/0day-ci/archive/2023/20231237.ztm5nblh-...@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/2023/20231237.ztm5nblh-...@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/20231237.ztm5nblh-...@intel.com/
All errors (new ones prefixed by >>):
In file included from include/trace/define_trace.h:102,
from drivers/bus/mhi/host/trace.h:224,
from drivers/bus/mhi/host/init.c:24:
drivers/bus/mhi/host/./trace.h: In function
'trace_event_raw_event_mhi_process_ctrl_ev_ring':
>> drivers/bus/mhi/host/../common.h:144:58: error: invalid type argument of
>> '->' (have 'u64' {aka 'long long unsigned int'})
144 | #define MHI_TRE_GET_DWORD(tre, word)
le32_to_cpu((tre)->dword[(word)])
| ^~
include/trace/trace_events.h:402:11: note: in definition of macro
'DECLARE_EVENT_CLASS'
402 | { assign; }
\
| ^~
include/trace/trace_events.h:44:30: note: in expansion of macro 'PARAMS'
44 | PARAMS(assign), \
| ^~
drivers/bus/mhi/host/./trace.h:123:1: note: in expansion of macro
'TRACE_EVENT'
123 | TRACE_EVENT(mhi_process_ctrl_ev_ring,
| ^~~
drivers/bus/mhi/host/./trace.h:138:9: note: in expansion of macro
'TP_fast_assign'
138 | TP_fast_assign(
| ^~
include/linux/compiler_types.h:413:9: note: in expansion of macro
'__compiletime_assert'
413 | __compiletime_assert(condition, msg, prefix, suffix)
| ^~~~
include/linux/compiler_types.h:425:9: note: in expansion of macro
'_compiletime_assert'
425 | _compiletime_assert(condition, msg, __compiletime_assert_,
__COUNTER__)
| ^~~
include/linux/build_bug.h:39:37: note: in expansion of macro
'compiletime_assert'
39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
| ^~
include/linux/bitfield.h:71:17: note: in expansion of macro
'BUILD_BUG_ON_MSG'
71 | BUILD_BUG_ON_MSG(__bf_cast_unsigned(_mask, _mask) >
\
| ^~~~
include/linux/bitfield.h:61:43: note: in expansion of macro
'__unsigned_scalar_typeof'
61 | #define __bf_cast_unsigned(type, x)
((__unsigned_scalar_typeof(type))(x))
| ^~~~
include/linux/bitfield.h:72:34: note: in expansion of macro
'__bf_cast_unsigned'
72 | __bf_cast_unsigned(_reg, ~0ull),
\
| ^~
include/linux/bitfield.h:154:17: note: in expansion of macro
'__BF_FIELD_CHECK'
154 | __BF_FIELD_CHECK(_mask, _reg, 0U, "FIELD_GET: ");
\
| ^~~~
drivers/bus/mhi/host/../common.h:159:41: note: in expansion of macro
'FIELD_GET'
159 | #define MHI_TRE_GET_EV_STATE(tre) FIELD_GET(GENMASK(31, 24),
(MHI_TRE_GET_DWORD(tre, 0)))
| ^
include/linux/byteorder/generic.h:89:21: note: in expansion of macro
'__le32_to_cpu'
89 | #define le32_to_cpu __le32_to_cpu
| ^
drivers/bus/mhi/host/../common.h:159:69: note: in expansion of macro
'MHI_TRE_GET_DWORD'
159 | #define MHI_TRE_GET_EV_STATE(tre) FIELD_GET(GENMASK(31, 24),
(MHI_TRE_GET_DWORD(tre, 0)))
|
^
drivers/bus/mhi/host/./trace.h:144:34: note: in expansion of macro
'MHI_TRE_GET_EV_STATE'
144 | __entry->state = MHI_TRE_GET_EV_STATE(rp);
| ^~~~
>> drivers/bus/mhi/host/../common.h:144:58: error: invalid type argument of
&g
Re: [POC 1/7] livepatch: Add callbacks for introducing and removing states
Hi Petr,
kernel test robot noticed the following build warnings:
[auto build test WARNING on shuah-kselftest/next]
[also build test WARNING on shuah-kselftest/fixes linus/master v6.6
next-20231110]
[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/Petr-Mladek/livepatch-Add-callbacks-for-introducing-and-removing-states/2023-014906
base:
https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next
patch link:
https://lore.kernel.org/r/20231110170428.6664-2-pmladek%40suse.com
patch subject: [POC 1/7] livepatch: Add callbacks for introducing and removing
states
config: x86_64-rhel-8.3-rust
(https://download.01.org/0day-ci/archive/2023/20231107.avvipri2-...@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git
ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/2023/20231107.avvipri2-...@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/20231107.avvipri2-...@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/livepatch/state.c:121:6: warning: no previous prototype for function
>> 'is_state_in_other_patches' [-Wmissing-prototypes]
bool is_state_in_other_patches(struct klp_patch *patch, struct klp_state
*state)
^
kernel/livepatch/state.c:121:1: note: declare 'static' if the function is
not intended to be used outside of this translation unit
bool is_state_in_other_patches(struct klp_patch *patch, struct klp_state
*state)
^
static
1 warning generated.
vim +/is_state_in_other_patches +121 kernel/livepatch/state.c
120
> 121 bool is_state_in_other_patches(struct klp_patch *patch, struct
> klp_state *state)
122 {
123 struct klp_patch *old_patch;
124 struct klp_state *old_state;
125
126 klp_for_each_patch(old_patch) {
127 if (old_patch == patch)
128 continue;
129
130 klp_for_each_state(old_patch, old_state) {
131 if (old_state->id == state->id)
132 return true;
133 }
134 }
135
136 return false;
137 }
138
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [POC 5/7] livepatch: Convert klp module callbacks tests into livepatch module tests
Hi Petr, kernel test robot noticed the following build errors: [auto build test ERROR on shuah-kselftest/next] [also build test ERROR on shuah-kselftest/fixes linus/master v6.6 next-20231110] [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/Petr-Mladek/livepatch-Add-callbacks-for-introducing-and-removing-states/2023-014906 base: https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next patch link: https://lore.kernel.org/r/20231110170428.6664-6-pmladek%40suse.com patch subject: [POC 5/7] livepatch: Convert klp module callbacks tests into livepatch module tests config: s390-defconfig (https://download.01.org/0day-ci/archive/2023/20230928.ui5nizht-...@intel.com/config) compiler: s390-linux-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/2023/20230928.ui5nizht-...@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/20230928.ui5nizht-...@intel.com/ All errors (new ones prefixed by >>): >> make[5]: *** No rule to make target 'lib/livepatch/test_klp_speaker2.o', >> needed by 'lib/livepatch/'. >> make[5]: *** No rule to make target >> 'lib/livepatch/test_klp_speaker_livepatch2.o', needed by 'lib/livepatch/'. make[5]: *** [scripts/Makefile.build:243: lib/livepatch/test_klp_speaker.o] Error 1 make[5]: *** [scripts/Makefile.build:243: lib/livepatch/test_klp_speaker_livepatch.o] Error 1 make[5]: Target 'lib/livepatch/' not remade because of errors. -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [POC 1/7] livepatch: Add callbacks for introducing and removing states
Hi Petr,
kernel test robot noticed the following build warnings:
[auto build test WARNING on shuah-kselftest/next]
[also build test WARNING on shuah-kselftest/fixes linus/master v6.6
next-20231110]
[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/Petr-Mladek/livepatch-Add-callbacks-for-introducing-and-removing-states/2023-014906
base:
https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next
patch link:
https://lore.kernel.org/r/20231110170428.6664-2-pmladek%40suse.com
patch subject: [POC 1/7] livepatch: Add callbacks for introducing and removing
states
config: x86_64-randconfig-006-2023
(https://download.01.org/0day-ci/archive/2023/20230829.ukc9giug-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/2023/20230829.ukc9giug-...@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/20230829.ukc9giug-...@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/livepatch/state.c:121:6: warning: no previous prototype for
>> 'is_state_in_other_patches' [-Wmissing-prototypes]
121 | bool is_state_in_other_patches(struct klp_patch *patch, struct
klp_state *state)
| ^
vim +/is_state_in_other_patches +121 kernel/livepatch/state.c
120
> 121 bool is_state_in_other_patches(struct klp_patch *patch, struct
> klp_state *state)
122 {
123 struct klp_patch *old_patch;
124 struct klp_state *old_state;
125
126 klp_for_each_patch(old_patch) {
127 if (old_patch == patch)
128 continue;
129
130 klp_for_each_state(old_patch, old_state) {
131 if (old_state->id == state->id)
132 return true;
133 }
134 }
135
136 return false;
137 }
138
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v1] Ftrace: make sched_wakeup can focus on the target process
Hello,
kernel test robot noticed "BUG:kernel_NULL_pointer_dereference,address" on:
commit: e70b12f847f6d1b5db838c0eefa9d1d00c1591bd ("[PATCH v1] Ftrace: make
sched_wakeup can focus on the target process")
url:
https://github.com/intel-lab-lkp/linux/commits/Jinyu-Tang/Ftrace-make-sched_wakeup-can-focus-on-the-target-process/20231009-234127
base: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git
94f6f0550c625fab1f373bb86a6669b45e9748b3
patch link:
https://lore.kernel.org/all/20231009153714.10743-1-tangji...@tinylab.org/
patch subject: [PATCH v1] Ftrace: make sched_wakeup can focus on the target
process
in testcase: boot
compiler: gcc-7
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+-+--++
| | v6.6-rc5 | e70b12f847 |
+-+--++
| boot_successes | 33 | 0 |
| boot_failures | 0| 18 |
| BUG:kernel_NULL_pointer_dereference,address | 0| 18 |
| Oops:#[##] | 0| 18 |
| EIP:__kmem_cache_alloc_lru | 0| 18 |
| Kernel_panic-not_syncing:Fatal_exception| 0| 18 |
+-+--++
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-lkp/202310201530.46065346-oliver.s...@intel.com
[6.082261][T1] BUG: kernel NULL pointer dereference, address: 000c
[6.083178][T1] #PF: supervisor read access in kernel mode
[6.083178][T1] #PF: error_code(0x) - not-present page
[6.083178][T1] *pde =
[6.083178][T1] Oops: [#1]
[6.083178][T1] CPU: 0 PID: 1 Comm: swapper Not tainted
6.6.0-rc5-1-ge70b12f847f6 #1
[ 6.083178][ T1] EIP: __kmem_cache_alloc_lru+0x1d/0x88
[ 6.083178][ T1] Code: 04 eb a7 31 db e9 a5 fe ff ff 8d 76 00 3e 8d 74 26 00 55
b9 ff ff ff ff 89 e5 83 ec 18 89 5d f4 89 c3 89 75 f8 89 7d fc 89 d7 <8b> 40 0c
89 04 24 89 d8 e8 ca fd ff ff 8b 55 04 89 c6 a1 e4 38 25
All code
0: 04 eb add$0xeb,%al
2: a7 cmpsl %es:(%rdi),%ds:(%rsi)
3: 31 db xor%ebx,%ebx
5: e9 a5 fe ff ff jmpq 0xfeaf
a: 8d 76 00lea0x0(%rsi),%esi
d: 3e 8d 74 26 00 lea%ds:0x0(%rsi,%riz,1),%esi
12: 55 push %rbp
13: b9 ff ff ff ff mov$0x,%ecx
18: 89 e5 mov%esp,%ebp
1a: 83 ec 18sub$0x18,%esp
1d: 89 5d f4mov%ebx,-0xc(%rbp)
20: 89 c3 mov%eax,%ebx
22: 89 75 f8mov%esi,-0x8(%rbp)
25: 89 7d fcmov%edi,-0x4(%rbp)
28: 89 d7 mov%edx,%edi
2a:* 8b 40 0cmov0xc(%rax),%eax <-- trapping
instruction
2d: 89 04 24mov%eax,(%rsp)
30: 89 d8 mov%ebx,%eax
32: e8 ca fd ff ff callq 0xfe01
37: 8b 55 04mov0x4(%rbp),%edx
3a: 89 c6 mov%eax,%esi
3c: a1 .byte 0xa1
3d: e4 38 in $0x38,%al
3f: 25 .byte 0x25
Code starting with the faulting instruction
===
0: 8b 40 0cmov0xc(%rax),%eax
3: 89 04 24mov%eax,(%rsp)
6: 89 d8 mov%ebx,%eax
8: e8 ca fd ff ff callq 0xfdd7
d: 8b 55 04mov0x4(%rbp),%edx
10: 89 c6 mov%eax,%esi
12: a1 .byte 0xa1
13: e4 38 in $0x38,%al
15: 25 .byte 0x25
[6.083178][T1] EAX: EBX: ECX: EDX: 0cc0
[6.083178][T1] ESI: c3213800 EDI: 0cc0 EBP: c3217d78 ESP: c3217d60
[6.083178][T1] DS: 007b ES: 007b FS: GS: SS: 0068 EFLAGS:
00010286
[6.083178][T1] CR0: 80050033 CR2: 000c CR3: 02364000 CR4: 000406d0
[6.083178][T1] DR0: DR1: DR2: DR3:
[6.083178][T1] DR6: fffe0ff0 DR7: 0400
[6.083178][T1] Call Trace:
[ 6.083178][ T1] ? show_regs (arch/x86/kernel/dumpstack.c:479)
[ 6.083178][ T1] ? __die_body (arch/x86/kernel/dumpstack.c:421)
[ 6.083178][ T1] ? __die (arch/x86/kernel/dumpstack.c:435)
[ 6.0
Re: [PATCH v2] bus: mhi: host: Add tracing support
Hi Krishna,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 3006adf3be79cde4d14b1800b963b82b6e5572e0]
url:
https://github.com/intel-lab-lkp/linux/commits/Krishna-chaitanya-chundru/bus-mhi-host-Add-tracing-support/20231017-120241
base: 3006adf3be79cde4d14b1800b963b82b6e5572e0
patch link:
https://lore.kernel.org/r/20231013-ftrace_support-v2-1-6e893ce010b5%40quicinc.com
patch subject: [PATCH v2] bus: mhi: host: Add tracing support
config: i386-randconfig-002-20231020
(https://download.01.org/0day-ci/archive/20231020/202310201110.s903hmed-...@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231020/202310201110.s903hmed-...@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/202310201110.s903hmed-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/bus/mhi/host/main.c:249:12: warning: no previous declaration for
>> 'mhi_to_physical' [-Wmissing-declarations]
dma_addr_t mhi_to_physical(struct mhi_ring *ring, void *addr)
^~~
vim +/mhi_to_physical +249 drivers/bus/mhi/host/main.c
248
> 249 dma_addr_t mhi_to_physical(struct mhi_ring *ring, void *addr)
250 {
251 return (addr - ring->base) + ring->iommu_base;
252 }
253
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v6 4/4] remoteproc: zynqmp: parse TCM from device tree
Hi Tanmay, kernel test robot noticed the following build warnings: [auto build test WARNING on a7d272979d3a89b117ca2c547dc8a465c4f28635] url: https://github.com/intel-lab-lkp/linux/commits/Tanmay-Shah/dt-bindings-remoteproc-add-Tightly-Coupled-Memory-TCM-bindings/20231017-120805 base: a7d272979d3a89b117ca2c547dc8a465c4f28635 patch link: https://lore.kernel.org/r/20231013042229.3954527-5-tanmay.shah%40amd.com patch subject: [PATCH v6 4/4] remoteproc: zynqmp: parse TCM from device tree config: arm64-randconfig-002-20231019 (https://download.01.org/0day-ci/archive/20231019/202310191806.njlsejwm-...@intel.com/config) compiler: aarch64-linux-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231019/202310191806.njlsejwm-...@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/202310191806.njlsejwm-...@intel.com/ All warnings (new ones prefixed by >>): drivers/remoteproc/xlnx_r5_remoteproc.c: In function 'zynqmp_r5_get_tcm_node_from_dt': >> drivers/remoteproc/xlnx_r5_remoteproc.c:1162:28: warning: array subscript >> 'struct mem_bank_data[0]' is partly outside array bounds of 'unsigned >> char[8]' [-Warray-bounds=] 1162 | tcm->da = (u32)abs_addr; |^~ In file included from include/linux/dma-mapping.h:8, from drivers/remoteproc/xlnx_r5_remoteproc.c:8: In function 'devm_kzalloc', inlined from 'zynqmp_r5_get_tcm_node_from_dt' at drivers/remoteproc/xlnx_r5_remoteproc.c:1143:10: include/linux/device.h:314:16: note: object of size 8 allocated by 'devm_kmalloc' 314 | return devm_kmalloc(dev, size, gfp | __GFP_ZERO); |^ drivers/remoteproc/xlnx_r5_remoteproc.c: In function 'zynqmp_r5_get_tcm_node_from_dt': drivers/remoteproc/xlnx_r5_remoteproc.c:1163:28: warning: array subscript 'struct mem_bank_data[0]' is partly outside array bounds of 'unsigned char[8]' [-Warray-bounds=] 1163 | tcm->size = (u32)size; |^~ In function 'devm_kzalloc', inlined from 'zynqmp_r5_get_tcm_node_from_dt' at drivers/remoteproc/xlnx_r5_remoteproc.c:1143:10: include/linux/device.h:314:16: note: object of size 8 allocated by 'devm_kmalloc' 314 | return devm_kmalloc(dev, size, gfp | __GFP_ZERO); |^ drivers/remoteproc/xlnx_r5_remoteproc.c: In function 'zynqmp_r5_get_tcm_node_from_dt': drivers/remoteproc/xlnx_r5_remoteproc.c:1172:28: warning: array subscript 'struct mem_bank_data[0]' is partly outside array bounds of 'unsigned char[8]' [-Warray-bounds=] 1172 | tcm->addr = (u32)res->start; |^~ In function 'devm_kzalloc', inlined from 'zynqmp_r5_get_tcm_node_from_dt' at drivers/remoteproc/xlnx_r5_remoteproc.c:1143:10: include/linux/device.h:314:16: note: object of size 8 allocated by 'devm_kmalloc' 314 | return devm_kmalloc(dev, size, gfp | __GFP_ZERO); |^ drivers/remoteproc/xlnx_r5_remoteproc.c: In function 'zynqmp_r5_get_tcm_node_from_dt': drivers/remoteproc/xlnx_r5_remoteproc.c:1173:28: warning: array subscript 'struct mem_bank_data[0]' is partly outside array bounds of 'unsigned char[8]' [-Warray-bounds=] 1173 | tcm->bank_name = (char *)res->name; |^~ In function 'devm_kzalloc', inlined from 'zynqmp_r5_get_tcm_node_from_dt' at drivers/remoteproc/xlnx_r5_remoteproc.c:1143:10: include/linux/device.h:314:16: note: object of size 8 allocated by 'devm_kmalloc' 314 | return devm_kmalloc(dev, size, gfp | __GFP_ZERO); |^ In file included from include/linux/device.h:17: drivers/remoteproc/xlnx_r5_remoteproc.c: In function 'zynqmp_r5_get_tcm_node_from_dt': drivers/remoteproc/xlnx_r5_remoteproc.c:1174:74: warning: array subscript 'struct mem_bank_data[0]' is partly outside array bounds of 'unsigned char[8]' [-Warray-bounds=] 1174 | res = devm_request_mem_region(dev, tcm->addr, tcm->size, | ^~ include/linux/ioport.h:306:63: note: in definition of macro 'devm_request_mem_region' 306 | __devm_request_region(dev, _resource, (start), (n), (name)) | ^ In function 'devm_kzalloc', inlined f
Re: [PATCH] dt-bindings: Drop kernel copy of common reserved-memory bindings
Hi Rob, kernel test robot noticed the following build errors: [auto build test ERROR on robh/for-next] [also build test ERROR on krzk-dt/for-next remoteproc/rproc-next broonie-sound/for-next linus/master v6.6-rc6 next-20231018] [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/Rob-Herring/dt-bindings-Drop-kernel-copy-of-common-reserved-memory-bindings/20231017-125913 base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next patch link: https://lore.kernel.org/r/20231013200851.347042-1-robh%40kernel.org patch subject: [PATCH] dt-bindings: Drop kernel copy of common reserved-memory bindings config: arm64-allyesconfig (https://download.01.org/0day-ci/archive/20231019/202310191537.20z1aolb-...@intel.com/config) compiler: aarch64-linux-gcc (GCC) 13.2.0 reproduce: (https://download.01.org/0day-ci/archive/20231019/202310191537.20z1aolb-...@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/202310191537.20z1aolb-...@intel.com/ All errors (new ones prefixed by >>): sort: -:2: disorder: 2023.8.dev2+gd5e5147 >> ERROR: dtschema minimum version is v2023.9 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
[tip:sched/core] [sched/numa] f169c62ff7: autonuma-benchmark.numa01.seconds -32.0% improvement
Hello,
kernel test robot noticed a -32.0% improvement of
autonuma-benchmark.numa01.seconds on:
commit: f169c62ff7cd1acf8bac8ae17bfeafa307d9e6fa ("sched/numa: Complete
scanning of inactive VMAs when there is no alternative")
https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git sched/core
testcase: autonuma-benchmark
test machine: 96 threads 2 sockets Intel(R) Xeon(R) Platinum 8260L CPU @
2.40GHz (Cascade Lake) with 128G memory
parameters:
iterations: 4x
test: _HARD_BIND
cpufreq_governor: performance
Details are as below:
-->
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231018/202310182223.6ef26fcb-oliver.s...@intel.com
=
compiler/cpufreq_governor/iterations/kconfig/rootfs/tbox_group/test/testcase:
gcc-12/performance/4x/x86_64-rhel-8.3/debian-11.1-x86_64-20220510.cgz/lkp-csl-2sp3/_HARD_BIND/autonuma-benchmark
commit:
b7a5b537c5 ("sched/numa: Complete scanning of partial VMAs regardless of PID
activity")
f169c62ff7 ("sched/numa: Complete scanning of inactive VMAs when there is no
alternative")
b7a5b537c55c088d f169c62ff7cd1acf8bac8ae17bf
---
%stddev %change %stddev
\ |\
0.00 ± 58% +3290.8% 0.06 ± 30% vmstat.procs.b
2.101e+10 ± 6% -47.7% 1.099e+10 ± 5% cpuidle..time
21679574 ± 6% -47.8% 11321089 ± 5% cpuidle..usage
2441 -25.2% 1826 ± 2% uptime.boot
25666 ± 5% -40.3% 15332 ± 3% uptime.idle
208968 ± 8% -11.6% 184676 ± 3% meminfo.Active
208280 ± 8% -11.7% 183990 ± 3% meminfo.Active(anon)
221680 ± 8% -11.7% 195741 ± 2% meminfo.Shmem
3154708 ± 7% -12.1%2773727 ± 4% numa-numastat.node0.local_node
3621021 ± 4% -12.9%3154008 ± 3% numa-numastat.node0.numa_hit
3424075 ± 5% -19.2%2767342 ± 3% numa-numastat.node1.local_node
3659250 ± 4% -15.8%3079449 ± 3% numa-numastat.node1.numa_hit
3620012 ± 4% -12.9%3153670 ± 3% numa-vmstat.node0.numa_hit
3153693 ± 7% -12.1%2773388 ± 4% numa-vmstat.node0.numa_local
3657708 ± 4% -15.8%3078660 ± 3% numa-vmstat.node1.numa_hit
3422533 ± 5% -19.2%2766552 ± 3% numa-vmstat.node1.numa_local
0.03 ± 31%+840.9% 0.29 ±179%
perf-sched.sch_delay.avg.ms.exit_to_user_mode_loop.exit_to_user_mode_prepare.syscall_exit_to_user_mode.do_syscall_64
2.34 ± 49% -83.7% 0.38 ±194%
perf-sched.sch_delay.max.ms.__cond_resched.down_write_killable.setup_arg_pages.load_elf_binary.search_binary_handler
948.50 ± 16% -30.3% 661.33 ± 20%
perf-sched.wait_and_delay.count.exit_to_user_mode_loop.exit_to_user_mode_prepare.syscall_exit_to_user_mode.do_syscall_64
1142 ± 9% -24.3% 865.00 ± 9%
perf-sched.wait_and_delay.count.pipe_read.vfs_read.ksys_read.do_syscall_64
9.20 ± 6% -2.86.43 ± 5% mpstat.cpu.all.idle%
0.00 ± 14% +0.00.03 ± 28% mpstat.cpu.all.iowait%
2.25-0.51.73mpstat.cpu.all.irq%
0.08 ± 3% -0.00.06 ± 2% mpstat.cpu.all.soft%
2.18 ± 4% +0.52.69 ± 2% mpstat.cpu.all.sys%
474.78 -32.0% 322.76 ± 2% autonuma-benchmark.numa01.seconds
2386 -25.7% 1774 ± 2%
autonuma-benchmark.time.elapsed_time
2386 -25.7% 1774 ± 2%
autonuma-benchmark.time.elapsed_time.max
1298583 ± 2% -24.3% 983395 ± 3%
autonuma-benchmark.time.involuntary_context_switches
3120169-6.0%2932947
autonuma-benchmark.time.minor_page_faults
8443+3.9% 8771
autonuma-benchmark.time.percent_of_cpu_this_job_got
197252 -23.2% 151486 ± 2% autonuma-benchmark.time.user_time
26055 +45.4% 37896 ± 8%
autonuma-benchmark.time.voluntary_context_switches
42526 ± 9% -15.6% 35892 ± 10% turbostat.C1
0.03+0.00.05 ± 20% turbostat.C1E%
21430219 ± 6% -48.2% 11099622 ± 5% turbostat.C6
9.14 ± 6% -2.76.40 ± 5% turbostat.C6%
8.80 ± 6% -31.1% 6.06 ± 5% turbostat.CPU%c1
2.31e+08 -24.9% 1.735e+08 ± 2% turbostat.IRQ
37846 ± 7% -29.3% 26768 ± 9% turbostat.POLL
283.70+3.1% 292.44turbostat.PkgWatt
63.32 +16.3% 73.65turbostat.RAMWatt
52079 ± 8% -11.6% 46034 ± 3% proc-vmstat.nr_active_anon
1560738-1.8%1532470proc-vmstat.nr_anon_pages
3000
Re: [PATCH v2] bus: mhi: host: Add tracing support
Hi Krishna,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 3006adf3be79cde4d14b1800b963b82b6e5572e0]
url:
https://github.com/intel-lab-lkp/linux/commits/Krishna-chaitanya-chundru/bus-mhi-host-Add-tracing-support/20231017-120241
base: 3006adf3be79cde4d14b1800b963b82b6e5572e0
patch link:
https://lore.kernel.org/r/20231013-ftrace_support-v2-1-6e893ce010b5%40quicinc.com
patch subject: [PATCH v2] bus: mhi: host: Add tracing support
config: m68k-allyesconfig
(https://download.01.org/0day-ci/archive/20231017/202310171556.hmpbsvrx-...@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231017/202310171556.hmpbsvrx-...@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/202310171556.hmpbsvrx-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/bus/mhi/host/main.c:249:12: warning: no previous prototype for
>> 'mhi_to_physical' [-Wmissing-prototypes]
249 | dma_addr_t mhi_to_physical(struct mhi_ring *ring, void *addr)
|^~~
vim +/mhi_to_physical +249 drivers/bus/mhi/host/main.c
248
> 249 dma_addr_t mhi_to_physical(struct mhi_ring *ring, void *addr)
250 {
251 return (addr - ring->base) + ring->iommu_base;
252 }
253
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v2] module: Add CONFIG_MODULE_LOAD_IN_SEQUENCE option
Hi Joey, kernel test robot noticed the following build warnings: [auto build test WARNING on mcgrof/modules-next] [also build test WARNING on linus/master v6.6-rc5 next-20231012] [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/Joey-Jiao/module-Add-CONFIG_MODULE_LOAD_IN_SEQUENCE-option/20231011-154640 base: https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git modules-next patch link: https://lore.kernel.org/r/20231011074438.6098-1-quic_jiangenj%40quicinc.com patch subject: [PATCH v2] module: Add CONFIG_MODULE_LOAD_IN_SEQUENCE option config: um-i386_defconfig (https://download.01.org/0day-ci/archive/20231013/202310130206.f778hunp-...@intel.com/config) compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231013/202310130206.f778hunp-...@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/202310130206.f778hunp-...@intel.com/ All warnings (new ones prefixed by >>): kernel/module/main.c: In function 'do_init_module': kernel/module/main.c:2627:12: error: invalid storage class for function 'may_init_module' static int may_init_module(void) ^~~ kernel/module/main.c:2636:13: error: invalid storage class for function 'finished_loading' static bool finished_loading(const char *name) ^~~~ kernel/module/main.c:2657:12: error: invalid storage class for function 'module_patient_check_exists' static int module_patient_check_exists(const char *name, ^~~ kernel/module/main.c:2701:12: error: invalid storage class for function 'add_unformed_module' static int add_unformed_module(struct module *mod) ^~~ kernel/module/main.c:2722:12: error: invalid storage class for function 'complete_formation' static int complete_formation(struct module *mod, struct load_info *info) ^~ kernel/module/main.c:2755:12: error: invalid storage class for function 'prepare_coming_module' static int prepare_coming_module(struct module *mod) ^ kernel/module/main.c:2773:12: error: invalid storage class for function 'unknown_module_param_cb' static int unknown_module_param_cb(char *param, char *val, const char *modname, ^~~ kernel/module/main.c:2793:12: error: invalid storage class for function 'early_mod_check' static int early_mod_check(struct load_info *info, int flags) ^~~ kernel/module/main.c:2829:12: error: invalid storage class for function 'load_module' static int load_module(struct load_info *info, const char __user *uargs, ^~~ >> kernel/module/main.c:3039:1: warning: 'alias' attribute ignored >> [-Wattributes] SYSCALL_DEFINE3(init_module, void __user *, umod, ^~~ In file included from kernel/module/main.c:26:0: include/linux/syscalls.h:247:21: error: invalid storage class for function '__do_sys_init_module' static inline long __do_sys##name(__MAP(x,__SC_DECL,__VA_ARGS__));\ ^ include/linux/syscalls.h:230:2: note: in expansion of macro '__SYSCALL_DEFINEx' __SYSCALL_DEFINEx(x, sname, __VA_ARGS__) ^ include/linux/syscalls.h:221:36: note: in expansion of macro 'SYSCALL_DEFINEx' #define SYSCALL_DEFINE3(name, ...) SYSCALL_DEFINEx(3, _##name, __VA_ARGS__) ^~~ kernel/module/main.c:3039:1: note: in expansion of macro 'SYSCALL_DEFINE3' SYSCALL_DEFINE3(init_module, void __user *, umod, ^~~ include/linux/syscalls.h:249:18: error: static declaration of '__se_sys_init_module' follows non-static declaration asmlinkage long __se_sys##name(__MAP(x,__SC_LONG,__VA_ARGS__)) \ ^ include/linux/syscalls.h:230:2: note: in expansion of macro '__SYSCALL_DEFINEx' __SYSCALL_DEFINEx(x, sname, __VA_ARGS__) ^ include/linux/syscalls.h:221:36: note: in expansion of macro 'SYSCALL_DEFINEx' #define SYSCALL_DEFINE3(name, ...) SYSCALL_DEFINEx(3, _##name, __VA_ARGS__) ^~~ kernel/module/main.c:3039:1: note: in expansion of macro 'SYSCALL_DEFINE3' SYSCALL_DEFINE3(init_module, void __user *, umod, ^~~ include/linux/syscalls.h:248:18: note: previous declaration of '__se_sys_init_module' was here asmlinkage long __se
Re: [PATCH v2] module: Add CONFIG_MODULE_LOAD_IN_SEQUENCE option
Hi Joey, kernel test robot noticed the following build errors: [auto build test ERROR on mcgrof/modules-next] [also build test ERROR on linus/master v6.6-rc5 next-20231012] [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/Joey-Jiao/module-Add-CONFIG_MODULE_LOAD_IN_SEQUENCE-option/20231011-154640 base: https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git modules-next patch link: https://lore.kernel.org/r/20231011074438.6098-1-quic_jiangenj%40quicinc.com patch subject: [PATCH v2] module: Add CONFIG_MODULE_LOAD_IN_SEQUENCE option config: um-allnoconfig (https://download.01.org/0day-ci/archive/20231013/202310130236.lybpy0lh-...@intel.com/config) compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231013/202310130236.lybpy0lh-...@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/202310130236.lybpy0lh-...@intel.com/ All errors (new ones prefixed by >>): In file included from kernel/module/main.c:14: In file included from include/linux/trace_events.h:9: In file included from include/linux/hardirq.h:11: In file included from arch/um/include/asm/hardirq.h:5: In file included from include/asm-generic/hardirq.h:17: In file included from include/linux/irq.h:20: In file included from include/linux/io.h:13: In file included from arch/um/include/asm/io.h:24: include/asm-generic/io.h:547:31: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 547 | val = __raw_readb(PCI_IOBASE + addr); | ~~ ^ include/asm-generic/io.h:560:61: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 560 | val = __le16_to_cpu((__le16 __force)__raw_readw(PCI_IOBASE + addr)); | ~~ ^ include/uapi/linux/byteorder/little_endian.h:37:51: note: expanded from macro '__le16_to_cpu' 37 | #define __le16_to_cpu(x) ((__force __u16)(__le16)(x)) | ^ In file included from kernel/module/main.c:14: In file included from include/linux/trace_events.h:9: In file included from include/linux/hardirq.h:11: In file included from arch/um/include/asm/hardirq.h:5: In file included from include/asm-generic/hardirq.h:17: In file included from include/linux/irq.h:20: In file included from include/linux/io.h:13: In file included from arch/um/include/asm/io.h:24: include/asm-generic/io.h:573:61: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 573 | val = __le32_to_cpu((__le32 __force)__raw_readl(PCI_IOBASE + addr)); | ~~ ^ include/uapi/linux/byteorder/little_endian.h:35:51: note: expanded from macro '__le32_to_cpu' 35 | #define __le32_to_cpu(x) ((__force __u32)(__le32)(x)) | ^ In file included from kernel/module/main.c:14: In file included from include/linux/trace_events.h:9: In file included from include/linux/hardirq.h:11: In file included from arch/um/include/asm/hardirq.h:5: In file included from include/asm-generic/hardirq.h:17: In file included from include/linux/irq.h:20: In file included from include/linux/io.h:13: In file included from arch/um/include/asm/io.h:24: include/asm-generic/io.h:584:33: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 584 | __raw_writeb(value, PCI_IOBASE + addr); | ~~ ^ include/asm-generic/io.h:594:59: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 594 | __raw_writew((u16 __force)cpu_to_le16(value), PCI_IOBASE + addr); | ~~ ^ include/asm-generic/io.h:604:59: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic] 604 | __raw_writel((u32 __force)cpu_to_le32(value), PCI_IOBASE + addr); | ~~ ^ include/asm-generic/io.h:692:20: warning: performing pointer arit
Re: [PATCH v2] module: Add CONFIG_MODULE_LOAD_IN_SEQUENCE option
Hi Joey, kernel test robot noticed the following build warnings: [auto build test WARNING on mcgrof/modules-next] [also build test WARNING on linus/master v6.6-rc5 next-20231011] [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/Joey-Jiao/module-Add-CONFIG_MODULE_LOAD_IN_SEQUENCE-option/20231011-154640 base: https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git modules-next patch link: https://lore.kernel.org/r/20231011074438.6098-1-quic_jiangenj%40quicinc.com patch subject: [PATCH v2] module: Add CONFIG_MODULE_LOAD_IN_SEQUENCE option config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20231011/202310111840.ufgoxyfm-...@intel.com/config) compiler: m68k-linux-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231011/202310111840.ufgoxyfm-...@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/202310111840.ufgoxyfm-...@intel.com/ All warnings (new ones prefixed by >>): kernel/module/main.c: In function 'do_init_module': kernel/module/main.c:2627:12: error: invalid storage class for function 'may_init_module' 2627 | static int may_init_module(void) |^~~ kernel/module/main.c:2636:13: error: invalid storage class for function 'finished_loading' 2636 | static bool finished_loading(const char *name) | ^~~~ kernel/module/main.c:2657:12: error: invalid storage class for function 'module_patient_check_exists' 2657 | static int module_patient_check_exists(const char *name, |^~~ kernel/module/main.c:2701:12: error: invalid storage class for function 'add_unformed_module' 2701 | static int add_unformed_module(struct module *mod) |^~~ kernel/module/main.c:2722:12: error: invalid storage class for function 'complete_formation' 2722 | static int complete_formation(struct module *mod, struct load_info *info) |^~ kernel/module/main.c:2755:12: error: invalid storage class for function 'prepare_coming_module' 2755 | static int prepare_coming_module(struct module *mod) |^ kernel/module/main.c:2773:12: error: invalid storage class for function 'unknown_module_param_cb' 2773 | static int unknown_module_param_cb(char *param, char *val, const char *modname, |^~~ kernel/module/main.c:2793:12: error: invalid storage class for function 'early_mod_check' 2793 | static int early_mod_check(struct load_info *info, int flags) |^~~ kernel/module/main.c:2829:12: error: invalid storage class for function 'load_module' 2829 | static int load_module(struct load_info *info, const char __user *uargs, |^~~ In file included from include/linux/compiler_types.h:125, from : >> include/linux/compiler-gcc.h:132:33: warning: 'alias' attribute ignored >> [-Wattributes] 132 | #define __diag(s) _Pragma(__diag_str(GCC diagnostic s)) | ^~~ include/linux/compiler-gcc.h:135:33: note: in expansion of macro '__diag' 135 | #define __diag_GCC_8(s) __diag(s) | ^~ include/linux/compiler-gcc.h:123:9: note: in expansion of macro '__diag_GCC_8' 123 | __diag_GCC_ ## version(__diag_GCC_ ## severity s) | ^~~ include/linux/compiler_types.h:416:9: note: in expansion of macro '__diag_GCC' 416 | __diag_ ## compiler(version, ignore, option) | ^~~ include/linux/syscalls.h:242:9: note: in expansion of macro '__diag_ignore' 242 | __diag_ignore(GCC, 8, "-Wattribute-alias", \ | ^ include/linux/syscalls.h:230:9: note: in expansion of macro '__SYSCALL_DEFINEx' 230 | __SYSCALL_DEFINEx(x, sname, __VA_ARGS__) | ^ include/linux/syscalls.h:221:36: note: in expansion of macro 'SYSCALL_DEFINEx' 221 | #define SYSCALL_DEFINE3(name, ...) SYSCALL_DEFINEx(3, _##name, __VA_ARGS__) |^~~ kernel/module/main.c:3039:1: note: in expansion of macro 'SYSCALL_DEFINE3' 3039 | SYSCALL_DEFINE3(init_module, void __user *, umod, | ^~~ In file included from kernel/module
Re: [PATCH 01/10] appletalk: remove localtalk and ppp support
Hi Arnd,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20231009]
[cannot apply to linus/master v6.6-rc5 v6.6-rc4 v6.6-rc3 v6.6-rc5]
[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/Arnd-Bergmann/ieee802154-avoid-deprecated-ndo_do_ioctl-callback/20231009-222305
base: next-20231009
patch link:
https://lore.kernel.org/r/20231009141908.1767241-1-arnd%40kernel.org
patch subject: [PATCH 01/10] appletalk: remove localtalk and ppp support
config: x86_64-randconfig-002-20231011
(https://download.01.org/0day-ci/archive/20231011/202310111736.4mh6cf5c-...@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231011/202310111736.4mh6cf5c-...@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/202310111736.4mh6cf5c-...@intel.com/
All warnings (new ones prefixed by >>):
drivers/net/appletalk/ipddp.c: In function 'ipddp_create':
drivers/net/appletalk/ipddp.c:207:24: error: implicit declaration of
function 'atrtr_get_dev'; did you mean 'to_net_dev'?
[-Werror=implicit-function-declaration]
if ((rt->dev = atrtr_get_dev(>at)) == NULL) {
^
to_net_dev
>> drivers/net/appletalk/ipddp.c:207:22: warning: assignment makes pointer from
>> integer without a cast [-Wint-conversion]
if ((rt->dev = atrtr_get_dev(>at)) == NULL) {
^
cc1: some warnings being treated as errors
vim +207 drivers/net/appletalk/ipddp.c
^1da177e4c3f41 Linus Torvalds 2005-04-16 192
^1da177e4c3f41 Linus Torvalds 2005-04-16 193 /*
^1da177e4c3f41 Linus Torvalds 2005-04-16 194 * Create a routing entry. We
first verify that the
^1da177e4c3f41 Linus Torvalds 2005-04-16 195 * record does not already
exist. If it does we return -EEXIST
^1da177e4c3f41 Linus Torvalds 2005-04-16 196 */
^1da177e4c3f41 Linus Torvalds 2005-04-16 197 static int ipddp_create(struct
ipddp_route *new_rt)
^1da177e4c3f41 Linus Torvalds 2005-04-16 198 {
ce7e40c432ba84 Vlad Tsyrklevich 2017-01-09 199 struct ipddp_route *rt
= kzalloc(sizeof(*rt), GFP_KERNEL);
^1da177e4c3f41 Linus Torvalds 2005-04-16 200
^1da177e4c3f41 Linus Torvalds 2005-04-16 201 if (rt == NULL)
^1da177e4c3f41 Linus Torvalds 2005-04-16 202 return -ENOMEM;
^1da177e4c3f41 Linus Torvalds 2005-04-16 203
^1da177e4c3f41 Linus Torvalds 2005-04-16 204 rt->ip = new_rt->ip;
^1da177e4c3f41 Linus Torvalds 2005-04-16 205 rt->at = new_rt->at;
^1da177e4c3f41 Linus Torvalds 2005-04-16 206 rt->next = NULL;
^1da177e4c3f41 Linus Torvalds 2005-04-16 @207 if ((rt->dev =
atrtr_get_dev(>at)) == NULL) {
^1da177e4c3f41 Linus Torvalds 2005-04-16 208 kfree(rt);
^1da177e4c3f41 Linus Torvalds 2005-04-16 209 return
-ENETUNREACH;
^1da177e4c3f41 Linus Torvalds 2005-04-16 210 }
^1da177e4c3f41 Linus Torvalds 2005-04-16 211
5615968a708451 David S. Miller 2009-05-27 212
spin_lock_bh(_route_lock);
5615968a708451 David S. Miller 2009-05-27 213 if
(__ipddp_find_route(rt)) {
5615968a708451 David S. Miller 2009-05-27 214
spin_unlock_bh(_route_lock);
^1da177e4c3f41 Linus Torvalds 2005-04-16 215 kfree(rt);
^1da177e4c3f41 Linus Torvalds 2005-04-16 216 return -EEXIST;
^1da177e4c3f41 Linus Torvalds 2005-04-16 217 }
^1da177e4c3f41 Linus Torvalds 2005-04-16 218
^1da177e4c3f41 Linus Torvalds 2005-04-16 219 rt->next =
ipddp_route_list;
^1da177e4c3f41 Linus Torvalds 2005-04-16 220 ipddp_route_list = rt;
^1da177e4c3f41 Linus Torvalds 2005-04-16 221
5615968a708451 David S. Miller 2009-05-27 222
spin_unlock_bh(_route_lock);
5615968a708451 David S. Miller 2009-05-27 223
^1da177e4c3f41 Linus Torvalds 2005-04-16 224 return 0;
^1da177e4c3f41 Linus Torvalds 2005-04-16 225 }
^1da177e4c3f41 Linus Torvalds 2005-04-16 226
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH v1] Ftrace: make sched_wakeup can focus on the target process
Hi Jinyu, kernel test robot noticed the following build warnings: [auto build test WARNING on linus/master] [also build test WARNING on rostedt-trace/for-next v6.6-rc5 next-20231010] [cannot apply to rostedt-trace/for-next-urgent] [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/Jinyu-Tang/Ftrace-make-sched_wakeup-can-focus-on-the-target-process/20231009-234127 base: linus/master patch link: https://lore.kernel.org/r/20231009153714.10743-1-tangjinyu%40tinylab.org patch subject: [PATCH v1] Ftrace: make sched_wakeup can focus on the target process config: i386-randconfig-062-20231010 (https://download.01.org/0day-ci/archive/20231011/202310110813.fxuatrh0-...@intel.com/config) compiler: gcc-9 (Debian 9.3.0-22) 9.3.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231011/202310110813.fxuatrh0-...@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/202310110813.fxuatrh0-...@intel.com/ sparse warnings: (new ones prefixed by >>) >> kernel/trace/trace_sched_wakeup.c:368:1: sparse: sparse: symbol >> 'sched_wakeup_mutex' was not declared. Should it be static? -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
Re: [PATCH] bus: mhi: host: Add tracing support
Hi Krishna,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 3006adf3be79cde4d14b1800b963b82b6e5572e0]
url:
https://github.com/intel-lab-lkp/linux/commits/Krishna-chaitanya-chundru/bus-mhi-host-Add-tracing-support/20231005-231430
base: 3006adf3be79cde4d14b1800b963b82b6e5572e0
patch link:
https://lore.kernel.org/r/20231005-ftrace_support-v1-1-23a2f394fa49%40quicinc.com
patch subject: [PATCH] bus: mhi: host: Add tracing support
config: i386-randconfig-062-20231010
(https://download.01.org/0day-ci/archive/20231010/202310102355.6sea9ysi-...@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231010/202310102355.6sea9ysi-...@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/202310102355.6sea9ysi-...@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/bus/mhi/host/main.c:835:56: sparse: sparse: incorrect type in
>> argument 3 (different base types) @@ expected unsigned long long
>> [usertype] ptr @@ got restricted __le64 [usertype] ptr @@
drivers/bus/mhi/host/main.c:835:56: sparse: expected unsigned long long
[usertype] ptr
drivers/bus/mhi/host/main.c:835:56: sparse: got restricted __le64
[usertype] ptr
>> drivers/bus/mhi/host/main.c:835:78: sparse: sparse: incorrect type in
>> argument 4 (different base types) @@ expected int dword0 @@ got
>> restricted __le32 @@
drivers/bus/mhi/host/main.c:835:78: sparse: expected int dword0
drivers/bus/mhi/host/main.c:835:78: sparse: got restricted __le32
>> drivers/bus/mhi/host/main.c:836:63: sparse: sparse: incorrect type in
>> argument 5 (different base types) @@ expected int dword1 @@ got
>> restricted __le32 @@
drivers/bus/mhi/host/main.c:836:63: sparse: expected int dword1
drivers/bus/mhi/host/main.c:836:63: sparse: got restricted __le32
drivers/bus/mhi/host/main.c:1004:85: sparse: sparse: incorrect type in
argument 2 (different base types) @@ expected unsigned long long [usertype]
ptr @@ got restricted __le64 [usertype] ptr @@
drivers/bus/mhi/host/main.c:1004:85: sparse: expected unsigned long long
[usertype] ptr
drivers/bus/mhi/host/main.c:1004:85: sparse: got restricted __le64
[usertype] ptr
drivers/bus/mhi/host/main.c:1005:66: sparse: sparse: incorrect type in
argument 3 (different base types) @@ expected int dword0 @@ got
restricted __le32 @@
drivers/bus/mhi/host/main.c:1005:66: sparse: expected int dword0
drivers/bus/mhi/host/main.c:1005:66: sparse: got restricted __le32
drivers/bus/mhi/host/main.c:1005:86: sparse: sparse: incorrect type in
argument 4 (different base types) @@ expected int dword1 @@ got
restricted __le32 @@
drivers/bus/mhi/host/main.c:1005:86: sparse: expected int dword1
drivers/bus/mhi/host/main.c:1005:86: sparse: got restricted __le32
>> drivers/bus/mhi/host/main.c:1246:34: sparse: sparse: incorrect type in
>> argument 4 (different base types) @@ expected unsigned long long
>> [usertype] tre_ptr @@ got restricted __le64 [usertype] ptr @@
drivers/bus/mhi/host/main.c:1246:34: sparse: expected unsigned long long
[usertype] tre_ptr
drivers/bus/mhi/host/main.c:1246:34: sparse: got restricted __le64
[usertype] ptr
drivers/bus/mhi/host/main.c:1246:55: sparse: sparse: incorrect type in
argument 5 (different base types) @@ expected int dword0 @@ got
restricted __le32 @@
drivers/bus/mhi/host/main.c:1246:55: sparse: expected int dword0
drivers/bus/mhi/host/main.c:1246:55: sparse: got restricted __le32
drivers/bus/mhi/host/main.c:1246:74: sparse: sparse: incorrect type in
argument 6 (different base types) @@ expected int dword1 @@ got
restricted __le32 @@
drivers/bus/mhi/host/main.c:1246:74: sparse: expected int dword1
drivers/bus/mhi/host/main.c:1246:74: sparse: got restricted __le32
>> drivers/bus/mhi/host/main.c:834:80: sparse: sparse: non size-preserving
>> pointer to integer cast
drivers/bus/mhi/host/main.c:1245:75: sparse: sparse: non size-preserving
pointer to integer cast
vim +835 drivers/bus/mhi/host/main.c
799
800 int mhi_process_ctrl_ev_ring(struct mhi_controller *mhi_cntrl,
801 struct mhi_event *mhi_event,
802 u32 event_quota)
803 {
804 struct mhi_ring_element *dev_rp, *local_rp;
805 struct mhi_ring *ev_ring = _event->ring;
806 struct mhi_event_ctxt *er_ctxt =
807 _cntrl->mhi_ctxt->er_ctxt[mhi_event->er_index];
808 struct mhi_chan
Re: [PATCH 01/10] appletalk: remove localtalk and ppp support
Hi Arnd,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20231009]
[cannot apply to linus/master v6.6-rc5 v6.6-rc4 v6.6-rc3 v6.6-rc5]
[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/Arnd-Bergmann/ieee802154-avoid-deprecated-ndo_do_ioctl-callback/20231009-222305
base: next-20231009
patch link:
https://lore.kernel.org/r/20231009141908.1767241-1-arnd%40kernel.org
patch subject: [PATCH 01/10] appletalk: remove localtalk and ppp support
config: nios2-randconfig-001-20231010
(https://download.01.org/0day-ci/archive/20231010/202310101724.irnaop3r-...@intel.com/config)
compiler: nios2-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231010/202310101724.irnaop3r-...@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/202310101724.irnaop3r-...@intel.com/
All error/warnings (new ones prefixed by >>):
drivers/net/appletalk/ipddp.c: In function 'ipddp_create':
>> drivers/net/appletalk/ipddp.c:207:24: error: implicit declaration of
>> function 'atrtr_get_dev'; did you mean 'to_net_dev'?
>> [-Werror=implicit-function-declaration]
207 | if ((rt->dev = atrtr_get_dev(>at)) == NULL) {
|^
|to_net_dev
>> drivers/net/appletalk/ipddp.c:207:22: warning: assignment to 'struct
>> net_device *' from 'int' makes pointer from integer without a cast
>> [-Wint-conversion]
207 | if ((rt->dev = atrtr_get_dev(>at)) == NULL) {
| ^
cc1: some warnings being treated as errors
vim +207 drivers/net/appletalk/ipddp.c
^1da177e4c3f41 Linus Torvalds 2005-04-16 192
^1da177e4c3f41 Linus Torvalds 2005-04-16 193 /*
^1da177e4c3f41 Linus Torvalds 2005-04-16 194 * Create a routing entry. We
first verify that the
^1da177e4c3f41 Linus Torvalds 2005-04-16 195 * record does not already
exist. If it does we return -EEXIST
^1da177e4c3f41 Linus Torvalds 2005-04-16 196 */
^1da177e4c3f41 Linus Torvalds 2005-04-16 197 static int ipddp_create(struct
ipddp_route *new_rt)
^1da177e4c3f41 Linus Torvalds 2005-04-16 198 {
ce7e40c432ba84 Vlad Tsyrklevich 2017-01-09 199 struct ipddp_route *rt
= kzalloc(sizeof(*rt), GFP_KERNEL);
^1da177e4c3f41 Linus Torvalds 2005-04-16 200
^1da177e4c3f41 Linus Torvalds 2005-04-16 201 if (rt == NULL)
^1da177e4c3f41 Linus Torvalds 2005-04-16 202 return -ENOMEM;
^1da177e4c3f41 Linus Torvalds 2005-04-16 203
^1da177e4c3f41 Linus Torvalds 2005-04-16 204 rt->ip = new_rt->ip;
^1da177e4c3f41 Linus Torvalds 2005-04-16 205 rt->at = new_rt->at;
^1da177e4c3f41 Linus Torvalds 2005-04-16 206 rt->next = NULL;
^1da177e4c3f41 Linus Torvalds 2005-04-16 @207 if ((rt->dev =
atrtr_get_dev(>at)) == NULL) {
^1da177e4c3f41 Linus Torvalds 2005-04-16 208 kfree(rt);
^1da177e4c3f41 Linus Torvalds 2005-04-16 209 return
-ENETUNREACH;
^1da177e4c3f41 Linus Torvalds 2005-04-16 210 }
^1da177e4c3f41 Linus Torvalds 2005-04-16 211
5615968a708451 David S. Miller 2009-05-27 212
spin_lock_bh(_route_lock);
5615968a708451 David S. Miller 2009-05-27 213 if
(__ipddp_find_route(rt)) {
5615968a708451 David S. Miller 2009-05-27 214
spin_unlock_bh(_route_lock);
^1da177e4c3f41 Linus Torvalds 2005-04-16 215 kfree(rt);
^1da177e4c3f41 Linus Torvalds 2005-04-16 216 return -EEXIST;
^1da177e4c3f41 Linus Torvalds 2005-04-16 217 }
^1da177e4c3f41 Linus Torvalds 2005-04-16 218
^1da177e4c3f41 Linus Torvalds 2005-04-16 219 rt->next =
ipddp_route_list;
^1da177e4c3f41 Linus Torvalds 2005-04-16 220 ipddp_route_list = rt;
^1da177e4c3f41 Linus Torvalds 2005-04-16 221
5615968a708451 David S. Miller 2009-05-27 222
spin_unlock_bh(_route_lock);
5615968a708451 David S. Miller 2009-05-27 223
^1da177e4c3f41 Linus Torvalds 2005-04-16 224 return 0;
^1da177e4c3f41 Linus Torvalds 2005-04-16 225 }
^1da177e4c3f41 Linus Torvalds 2005-04-16 226
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH] bus: mhi: host: Add tracing support
Hi Krishna,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 3006adf3be79cde4d14b1800b963b82b6e5572e0]
url:
https://github.com/intel-lab-lkp/linux/commits/Krishna-chaitanya-chundru/bus-mhi-host-Add-tracing-support/20231005-231430
base: 3006adf3be79cde4d14b1800b963b82b6e5572e0
patch link:
https://lore.kernel.org/r/20231005-ftrace_support-v1-1-23a2f394fa49%40quicinc.com
patch subject: [PATCH] bus: mhi: host: Add tracing support
config: m68k-allyesconfig
(https://download.01.org/0day-ci/archive/20231006/202310060033.z0ojejxe-...@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231006/202310060033.z0ojejxe-...@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/202310060033.z0ojejxe-...@intel.com/
All warnings (new ones prefixed by >>):
drivers/bus/mhi/host/main.c: In function 'mhi_process_ctrl_ev_ring':
>> drivers/bus/mhi/host/main.c:834:74: warning: cast from pointer to integer of
>> different size [-Wpointer-to-int-cast]
834 |
trace_mhi_process_ctrl_ev_ring(mhi_cntrl->mhi_dev->name, (u64)(local_rp),
|
^
drivers/bus/mhi/host/main.c: In function 'mhi_gen_tre':
drivers/bus/mhi/host/main.c:1245:69: warning: cast from pointer to integer
of different size [-Wpointer-to-int-cast]
1245 | trace_mhi_gen_tre(mhi_cntrl->mhi_dev->name, mhi_chan->chan,
(u64)(mhi_tre),
| ^
--
drivers/bus/mhi/host/pm.c: In function 'mhi_pm_st_worker':
>> drivers/bus/mhi/host/pm.c:758:24: warning: unused variable 'dev'
>> [-Wunused-variable]
758 | struct device *dev = _cntrl->mhi_dev->dev;
|^~~
vim +834 drivers/bus/mhi/host/main.c
799
800 int mhi_process_ctrl_ev_ring(struct mhi_controller *mhi_cntrl,
801 struct mhi_event *mhi_event,
802 u32 event_quota)
803 {
804 struct mhi_ring_element *dev_rp, *local_rp;
805 struct mhi_ring *ev_ring = _event->ring;
806 struct mhi_event_ctxt *er_ctxt =
807 _cntrl->mhi_ctxt->er_ctxt[mhi_event->er_index];
808 struct mhi_chan *mhi_chan;
809 struct device *dev = _cntrl->mhi_dev->dev;
810 u32 chan;
811 int count = 0;
812 dma_addr_t ptr = le64_to_cpu(er_ctxt->rp);
813
814 /*
815 * This is a quick check to avoid unnecessary event processing
816 * in case MHI is already in error state, but it's still
possible
817 * to transition to error state while processing events
818 */
819 if (unlikely(MHI_EVENT_ACCESS_INVALID(mhi_cntrl->pm_state)))
820 return -EIO;
821
822 if (!is_valid_ring_ptr(ev_ring, ptr)) {
823 dev_err(_cntrl->mhi_dev->dev,
824 "Event ring rp points outside of the event
ring\n");
825 return -EIO;
826 }
827
828 dev_rp = mhi_to_virtual(ev_ring, ptr);
829 local_rp = ev_ring->rp;
830
831 while (dev_rp != local_rp) {
832 enum mhi_pkt_type type = MHI_TRE_GET_EV_TYPE(local_rp);
833
> 834
> trace_mhi_process_ctrl_ev_ring(mhi_cntrl->mhi_dev->name, (u64)(local_rp),
835 local_rp->ptr,
local_rp->dword[0],
836 local_rp->dword[1],
837
mhi_state_str(MHI_TRE_GET_EV_STATE(local_rp)));
838
839 switch (type) {
840 case MHI_PKT_TYPE_BW_REQ_EVENT:
841 {
842 struct mhi_link_info *link_info;
843
844 link_info = _cntrl->mhi_link_info;
845 write_lock_irq(_cntrl->pm_lock);
846 link_info->target_link_speed =
847 MHI_TRE_GET_EV_LINKSPEED(local_rp);
848 link_info->target_link_width =
849 MHI_TRE_GET_EV_LINKWIDTH(local_rp);
850 write_unlock_irq(_cntrl->pm_lock);
851 dev_dbg(dev, "Received BW_REQ event\n");
852 m
Re: [PATCH] [v3] ieee802154: ca8210: Fix a potential UAF in ca8210_probe
Hi Dinghao,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.6-rc3 next-20230929]
[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/Dinghao-Liu/ieee802154-ca8210-Fix-a-potential-UAF-in-ca8210_probe/20231001-135130
base: linus/master
patch link:
https://lore.kernel.org/r/20231001054949.14624-1-dinghao.liu%40zju.edu.cn
patch subject: [PATCH] [v3] ieee802154: ca8210: Fix a potential UAF in
ca8210_probe
config: m68k-allyesconfig
(https://download.01.org/0day-ci/archive/20231001/202310011548.qyqmuodi-...@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20231001/202310011548.qyqmuodi-...@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/202310011548.qyqmuodi-...@intel.com/
All warnings (new ones prefixed by >>):
drivers/net/ieee802154/ca8210.c: In function 'ca8210_register_ext_clock':
>> drivers/net/ieee802154/ca8210.c:2743:13: warning: unused variable 'ret'
>> [-Wunused-variable]
2743 | int ret = 0;
| ^~~
vim +/ret +2743 drivers/net/ieee802154/ca8210.c
ded845a781a578 Harry Morris 2017-03-28 2731
ded845a781a578 Harry Morris 2017-03-28 2732 /**
ded845a781a578 Harry Morris 2017-03-28 2733 * ca8210_register_ext_clock() -
Register ca8210's external clock with kernel
ded845a781a578 Harry Morris 2017-03-28 2734 * @spi: Pointer to target
ca8210 spi device
ded845a781a578 Harry Morris 2017-03-28 2735 *
ded845a781a578 Harry Morris 2017-03-28 2736 * Return: 0 or linux error code
ded845a781a578 Harry Morris 2017-03-28 2737 */
ded845a781a578 Harry Morris 2017-03-28 2738 static int
ca8210_register_ext_clock(struct spi_device *spi)
ded845a781a578 Harry Morris 2017-03-28 2739 {
ded845a781a578 Harry Morris 2017-03-28 2740struct device_node *np =
spi->dev.of_node;
ded845a781a578 Harry Morris 2017-03-28 2741struct ca8210_priv *priv =
spi_get_drvdata(spi);
ded845a781a578 Harry Morris 2017-03-28 2742struct ca8210_platform_data
*pdata = spi->dev.platform_data;
ded845a781a578 Harry Morris 2017-03-28 @2743int ret = 0;
ded845a781a578 Harry Morris 2017-03-28 2744
ded845a781a578 Harry Morris 2017-03-28 2745if (!np)
ded845a781a578 Harry Morris 2017-03-28 2746return -EFAULT;
ded845a781a578 Harry Morris 2017-03-28 2747
ded845a781a578 Harry Morris 2017-03-28 2748priv->clk =
clk_register_fixed_rate(
ded845a781a578 Harry Morris 2017-03-28 2749>dev,
ded845a781a578 Harry Morris 2017-03-28 2750np->name,
ded845a781a578 Harry Morris 2017-03-28 2751NULL,
ded845a781a578 Harry Morris 2017-03-28 27520,
ded845a781a578 Harry Morris 2017-03-28 2753pdata->extclockfreq
ded845a781a578 Harry Morris 2017-03-28 2754);
ded845a781a578 Harry Morris 2017-03-28 2755
ded845a781a578 Harry Morris 2017-03-28 2756if (IS_ERR(priv->clk)) {
ded845a781a578 Harry Morris 2017-03-28 2757dev_crit(>dev,
"Failed to register external clk\n");
ded845a781a578 Harry Morris 2017-03-28 2758return
PTR_ERR(priv->clk);
ded845a781a578 Harry Morris 2017-03-28 2759}
ded845a781a578 Harry Morris 2017-03-28 2760
d0603f3c78f0aa Dinghao Liu 2023-10-01 2761return of_clk_add_provider(np,
of_clk_src_simple_get, priv->clk);
ded845a781a578 Harry Morris 2017-03-28 2762 }
ded845a781a578 Harry Morris 2017-03-28 2763
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[linus:master] [tracing] 9fe41efaca: WARNING:at_kernel/trace/trace_events.c:#event_trace_self_tests_init
Hello,
kernel test robot noticed
"WARNING:at_kernel/trace/trace_events.c:#event_trace_self_tests_init" on:
commit: 9fe41efaca08416657efa8731c0d47ccb6a3f3eb ("tracing: Add synth event
generation test module")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: boot
compiler: gcc-7
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
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-lkp/202309242249.94de41a1-oliver.s...@intel.com
[ 43.576702][T1] [ cut here ]
[ 43.577569][ T1] WARNING: CPU: 1 PID: 1 at kernel/trace/trace_events.c:3403
event_trace_self_tests_init (kernel/trace/trace_events.c:3402
kernel/trace/trace_events.c:3546)
[ 43.579528][T1] Modules linked in:
[ 43.580160][T1] CPU: 1 PID: 1 Comm: swapper/0 Not tainted
5.5.0-rc6-00065-g9fe41efaca0841 #1
[ 43.581559][ T1] RIP: 0010:event_trace_self_tests_init
(kernel/trace/trace_events.c:3402 kernel/trace/trace_events.c:3546)
[ 43.582586][ T1] Code: fc 48 8d 7d 48 48 89 f8 48 c1 e8 03 42 80 3c 20 00 74
05 e8 fd 3b c6 fc f6 45 48 01 74 10 48 c7 c7 20 4a 91 8b e8 6f 10 8a fc <0f> 0b
eb 2c 31 d2 be 01 00 00 00 48 89 ef e8 b8 a1 9f fc e8 b6 fa
All code
0: fc cld
1: 48 8d 7d 48 lea0x48(%rbp),%rdi
5: 48 89 f8mov%rdi,%rax
8: 48 c1 e8 03 shr$0x3,%rax
c: 42 80 3c 20 00 cmpb $0x0,(%rax,%r12,1)
11: 74 05 je 0x18
13: e8 fd 3b c6 fc callq 0xfcc63c15
18: f6 45 48 01 testb $0x1,0x48(%rbp)
1c: 74 10 je 0x2e
1e: 48 c7 c7 20 4a 91 8bmov$0x8b914a20,%rdi
25: e8 6f 10 8a fc callq 0xfc8a1099
2a:* 0f 0b ud2 <-- trapping instruction
2c: eb 2c jmp0x5a
2e: 31 d2 xor%edx,%edx
30: be 01 00 00 00 mov$0x1,%esi
35: 48 89 efmov%rbp,%rdi
38: e8 b8 a1 9f fc callq 0xfc9fa1f5
3d: e8 .byte 0xe8
3e: b6 fa mov$0xfa,%dh
Code starting with the faulting instruction
===
0: 0f 0b ud2
2: eb 2c jmp0x30
4: 31 d2 xor%edx,%edx
6: be 01 00 00 00 mov$0x1,%esi
b: 48 89 efmov%rbp,%rdi
e: e8 b8 a1 9f fc callq 0xfc9fa1cb
13: e8 .byte 0xe8
14: b6 fa mov$0xfa,%dh
[ 43.585621][T1] RSP: :8883ac827dd8 EFLAGS: 00010286
[ 43.586569][T1] RAX: 001f RBX: 8c38ae60 RCX:
[ 43.587821][T1] RDX: 001f RSI: 0006 RDI:
ed1075904fb1
[ 43.589057][T1] RBP: 8883ad2d5618 R08: 001f1194 R09:
[ 43.590290][T1] R10: 0001 R11: R12:
dc00
[ 43.591532][T1] R13: 88837e7ed340 R14: 88837e5c6880 R15:
8c38cb78
[ 43.596827][T1] FS: () GS:8883af00()
knlGS:
[ 43.598225][T1] CS: 0010 DS: ES: CR0: 80050033
[ 43.599253][T1] CR2: CR3: 9a015000 CR4:
000406e0
[ 43.600508][T1] Call Trace:
[ 43.601044][ T1] ? test_work (kernel/trace/trace_events.c:3545)
[ 43.601718][ T1] do_one_initcall (init/main.c:1107)
[ 43.602455][ T1] ? boot_config_checksum (init/main.c:1098)
[ 43.603274][ T1] ? rcu_read_lock_sched_held (include/linux/lockdep.h:361
kernel/rcu/update.c:122)
[ 43.604158][ T1] ? rcu_read_lock_bh_held (kernel/rcu/update.c:117)
[ 43.604997][ T1] ? test_bit (arch/x86/include/asm/bitops.h:214
include/asm-generic/bitops/instrumented-non-atomic.h:111)
[ 43.605662][ T1] kernel_init_freeable (init/main.c:1174 init/main.c:1190
init/main.c:1210 init/main.c:1381)
[ 43.606481][ T1] ? rest_init (init/main.c:1285)
[ 43.607182][ T1] kernel_init (init/main.c:1290)
[ 43.607865][ T1] ? _raw_spin_unlock_irq (arch/x86/include/asm/irqflags.h:54
arch/x86/include/asm/irqflags.h:94 include/linux/spinlock_api_smp.h:168
kernel/locking/spinlock.c:199)
[ 43.608678][ T1] ? rest_init (init/main.c:1285)
[ 43.609368][ T1] ret_from_fork (arch/x86/entry/entry_64.S:358)
[ 43.610087][T1] irq event stamp: 6455462
[ 43.610784][ T1] hardirqs last enabled at (6455461): console_unlock
(arch/x86/include/asm/irqflags.h:41 (discriminator 2)
arch/x86/include/asm/irqflags.h:84 (discriminator 2)
kernel/printk/p
Re: [PATCH V2] tracing/timerlat: Hotplug support for the user-space interface
Hello,
kernel test robot noticed "WARNING:possible_recursive_locking_detected" on:
commit: d2618f89d9ede5e14fd2eb2d140fff1d31f4948b ("[PATCH V2] tracing/timerlat:
Hotplug support for the user-space interface")
url:
https://github.com/intel-lab-lkp/linux/commits/Daniel-Bristot-de-Oliveira/tracing-timerlat-Hotplug-support-for-the-user-space-interface/20230920-234738
base: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git
2cf0f715623872823a72e451243bbf555d10d032
patch link:
https://lore.kernel.org/all/6b9a5f306e488bc77bf8521faeade420a0adf3e4.1695224204.git.bris...@kernel.org/
patch subject: [PATCH V2] tracing/timerlat: Hotplug support for the user-space
interface
in testcase: boot
compiler: gcc-12
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
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-lkp/202309242253.a3803da4-oliver.s...@intel.com
[ 108.795325][T1] WARNING: possible recursive locking detected
[ 108.796115][T1] 6.6.0-rc2-00019-gd2618f89d9ed #1 Not tainted
[ 108.796898][T1]
[ 108.797664][T1] swapper/0/1 is trying to acquire lock:
[ 108.798384][ T1] 85550630 (cpu_hotplug_lock){}-{0:0}, at:
__cpuhp_setup_state (kernel/cpu.c:2553)
[ 108.799656][T1]
[ 108.799656][T1] but task is already holding lock:
[ 108.800596][ T1] 85550630 (cpu_hotplug_lock){}-{0:0}, at:
init_osnoise_tracer (kernel/trace/trace_osnoise.c:3186)
[ 108.801843][T1]
[ 108.801843][T1] other info that might help us debug this:
[ 108.802890][T1] Possible unsafe locking scenario:
[ 108.802890][T1]
[ 108.803843][T1]CPU0
[ 108.804266][T1]
[ 108.804685][T1] lock(cpu_hotplug_lock);
[ 108.805267][T1] lock(cpu_hotplug_lock);
[ 108.805845][T1]
[ 108.805845][T1] *** DEADLOCK ***
[ 108.805845][T1]
[ 108.806885][T1] May be due to missing lock nesting notation
[ 108.806885][T1]
[ 108.807952][T1] 1 lock held by swapper/0/1:
[ 108.808547][ T1] #0: 85550630 (cpu_hotplug_lock){}-{0:0}, at:
init_osnoise_tracer (kernel/trace/trace_osnoise.c:3186)
[ 108.809838][T1]
[ 108.809838][T1] stack backtrace:
[ 108.819007][T1] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
6.6.0-rc2-00019-gd2618f89d9ed #1
[ 108.821026][T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 108.823537][T1] Call Trace:
[ 108.824310][T1]
[ 108.824999][ T1] dump_stack_lvl (lib/dump_stack.c:107 (discriminator 4))
[ 108.826053][ T1] validate_chain (kernel/locking/lockdep.c:3857)
[ 108.827124][ T1] ? __pfx_validate_chain (kernel/locking/lockdep.c:3824)
[ 108.828310][ T1] ? mark_lock (kernel/locking/lockdep.c:4655 (discriminator
3))
[ 108.829327][ T1] __lock_acquire (kernel/locking/lockdep.c:5136)
[ 108.830430][ T1] ? __cpuhp_setup_state (kernel/cpu.c:2553)
[ 108.831632][ T1] lock_acquire (kernel/locking/lockdep.c:467
kernel/locking/lockdep.c:5755 kernel/locking/lockdep.c:5718)
[ 108.832576][ T1] ? __cpuhp_setup_state (kernel/cpu.c:2553)
[ 108.833259][ T1] ? __pfx_lock_acquire (kernel/locking/lockdep.c:5721)
[ 108.833944][ T1] ? __pfx___might_resched (kernel/sched/core.c:10142)
[ 108.834708][ T1] ? preempt_latency_start (include/linux/ftrace.h:974
kernel/sched/core.c:5825 kernel/sched/core.c:5822)
[ 108.835443][ T1] ? __pfx_init_osnoise_tracer
(kernel/trace/trace_osnoise.c:3162)
[ 108.836185][ T1] cpus_read_lock (include/linux/percpu-rwsem.h:53
kernel/cpu.c:489)
[ 108.836774][ T1] ? __cpuhp_setup_state (kernel/cpu.c:2553)
[ 108.837437][ T1] __cpuhp_setup_state (kernel/cpu.c:2553)
[ 108.838089][ T1] ? __pfx_osnoise_cpu_die (kernel/trace/trace_osnoise.c:2168)
[ 108.839689][ T1] ? __pfx_osnoise_cpu_init (kernel/trace/trace_osnoise.c:2159)
[ 108.840399][ T1] init_osnoise_tracer (kernel/trace/trace_osnoise.c:2180
kernel/trace/trace_osnoise.c:3187)
[ 108.841052][ T1] do_one_initcall (init/main.c:1232)
[ 108.841674][ T1] ? __pfx_do_one_initcall (init/main.c:1223)
[ 108.842388][ T1] do_initcalls (init/main.c:1293 init/main.c:1310)
[ 108.842971][ T1] kernel_init_freeable (init/main.c:1549)
[ 108.843629][ T1] ? __pfx_kernel_init (init/main.c:1429)
[ 108.844265][ T1] kernel_init (init/main.c:1439)
[ 108.844816][ T1] ? __pfx_kernel_init (init/main.c:1429)
[ 108.845440][ T1] ret_from_fork (arch/x86/kernel/process.c:153)
[ 108.846002][ T1] ? __pfx_kernel_init (init/main.c:1429)
[ 108.846634][ T1] ret_from_fork_asm (arch/x86/entry/entry_64.S:312)
[ 108.847259][T1]
[ 108.884553][T1] Loading compiled-in X.509 certificates
[ 109.254386][T1] kmemleak: Kernel memory leak detector initialized
Re: [PATCH] tracing/timerlat: Hotplug support for the user-space interface
Hi Daniel,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.6-rc1 next-20230915]
[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/Daniel-Bristot-de-Oliveira/tracing-timerlat-Hotplug-support-for-the-user-space-interface/20230915-230157
base: linus/master
patch link:
https://lore.kernel.org/r/b619d9fd08a3bb47018cf40afa95783844a3c1fd.1694789910.git.bristot%40kernel.org
patch subject: [PATCH] tracing/timerlat: Hotplug support for the user-space
interface
config: um-randconfig-002-20230916
(https://download.01.org/0day-ci/archive/20230916/202309160854.saw0rium-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20230916/202309160854.saw0rium-...@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/202309160854.saw0rium-...@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/trace/trace_osnoise.c:2125:13: warning:
>> 'timerlat_rm_per_cpu_interface' defined but not used [-Wunused-function]
2125 | static void timerlat_rm_per_cpu_interface(long cpu) {};
| ^
>> kernel/trace/trace_osnoise.c:2124:12: warning:
>> 'timerlat_add_per_cpu_interface' defined but not used [-Wunused-function]
2124 | static int timerlat_add_per_cpu_interface(long cpu) { return 0; };
|^~
vim +/timerlat_rm_per_cpu_interface +2125 kernel/trace/trace_osnoise.c
2112
2113 static void timerlat_rm_per_cpu_interface(long cpu)
2114 {
2115 struct dentry *cpu_dir = per_cpu_ptr(_per_cpu_dir,
cpu)->root;
2116
2117 if (cpu_dir) {
2118 tracefs_remove(cpu_dir);
2119 per_cpu_ptr(_per_cpu_dir, cpu)->root = NULL;
2120 per_cpu_ptr(_per_cpu_dir, cpu)->timerlat_fd =
NULL;
2121 }
2122 }
2123 #else
> 2124 static int timerlat_add_per_cpu_interface(long cpu) { return 0; };
> 2125 static void timerlat_rm_per_cpu_interface(long cpu) {};
2126 #endif
2127
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH 1/8] trace: add new DECLARE_EVENT_CLASS_PRINT_INIT class type
Hi Linyu, kernel test robot noticed the following build warnings: [auto build test WARNING on usb/usb-testing] [also build test WARNING on usb/usb-next usb/usb-linus linus/master v6.6-rc1 next-20230914] [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/Linyu-Yuan/trace-add-new-DECLARE_EVENT_CLASS_PRINT_INIT-class-type/20230914-180924 base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing patch link: https://lore.kernel.org/r/20230914100302.30274-2-quic_linyyuan%40quicinc.com patch subject: [PATCH 1/8] trace: add new DECLARE_EVENT_CLASS_PRINT_INIT class type config: arm-defconfig (https://download.01.org/0day-ci/archive/20230914/202309142216.gwm6q6l0-...@intel.com/config) compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230914/202309142216.gwm6q6l0-...@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/202309142216.gwm6q6l0-...@intel.com/ All warnings (new ones prefixed by >>): In file included from include/trace/events/migrate.h:8, from mm/rmap.c:83: >> include/linux/tracepoint.h:554: warning: "DECLARE_EVENT_CLASS_PRINT_INIT" >> redefined 554 | #define DECLARE_EVENT_CLASS_PRINT_INIT(name, proto, args, tstruct, assign, print, init) | In file included from include/trace/define_trace.h:103, from include/trace/events/tlb.h:62, from mm/rmap.c:82: include/trace/perf.h:59: note: this is the location of the previous definition 59 | #define DECLARE_EVENT_CLASS_PRINT_INIT(call, proto, args, tstruct, assign, print, init) \ | >> include/linux/tracepoint.h:580: warning: "TRACE_EVENT_PRINT_INIT" redefined 580 | #define TRACE_EVENT_PRINT_INIT(name, proto, args, struct, assign, print, init) \ | In file included from include/trace/define_trace.h:102: include/trace/trace_events.h:49: note: this is the location of the previous definition 49 | #define TRACE_EVENT_PRINT_INIT(name, proto, args, tstruct, assign, print, init) \ | -- In file included from include/trace/events/net.h:12, from net/core/net-traces.c:31: >> include/linux/tracepoint.h:554: warning: "DECLARE_EVENT_CLASS_PRINT_INIT" >> redefined 554 | #define DECLARE_EVENT_CLASS_PRINT_INIT(name, proto, args, tstruct, assign, print, init) | In file included from include/trace/define_trace.h:103, from include/trace/events/skb.h:95, from net/core/net-traces.c:30: include/trace/perf.h:59: note: this is the location of the previous definition 59 | #define DECLARE_EVENT_CLASS_PRINT_INIT(call, proto, args, tstruct, assign, print, init) \ | >> include/linux/tracepoint.h:580: warning: "TRACE_EVENT_PRINT_INIT" redefined 580 | #define TRACE_EVENT_PRINT_INIT(name, proto, args, struct, assign, print, init) \ | In file included from include/trace/define_trace.h:102: include/trace/trace_events.h:49: note: this is the location of the previous definition 49 | #define TRACE_EVENT_PRINT_INIT(name, proto, args, tstruct, assign, print, init) \ | In file included from include/trace/events/napi.h:9, from net/core/net-traces.c:32: >> include/linux/tracepoint.h:554: warning: "DECLARE_EVENT_CLASS_PRINT_INIT" >> redefined 554 | #define DECLARE_EVENT_CLASS_PRINT_INIT(name, proto, args, tstruct, assign, print, init) | In file included from include/trace/define_trace.h:103, from include/trace/events/net.h:319: include/trace/perf.h:59: note: this is the location of the previous definition 59 | #define DECLARE_EVENT_CLASS_PRINT_INIT(call, proto, args, tstruct, assign, print, init) \ | >> include/linux/tracepoint.h:580: warning: "TRACE_EVENT_PRINT_INIT" redefined 580 | #define TRACE_EVENT_PRINT_INIT(name, proto, args, struct, assign, print, init) \ | In file included from include/trace/define_trace.h:102: include/trace/trace_events.h:49: note: this is the location of the previous definition 49 | #define TRACE_EVENT_PRINT_INIT(name, proto, args, tstruct, assign, print, init) \ | In file included from include/trace/events/sock.h:10, from net/core/net-traces.c:33: >> include/linux/tracepoint.h:554: warning: "DECLARE_EVENT_CLASS_PRINT_INIT"
Re: [PATCH v6 7/9] acpi/nfit: Move handler installing logic to driver
Hi Michal,
kernel test robot noticed the following build warnings:
[auto build test WARNING on rafael-pm/linux-next]
[also build test WARNING on nvdimm/libnvdimm-for-next]
[cannot apply to nvdimm/dax-misc]
[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/Michal-Wilczynski/acpi-bus-Introduce-wrappers-for-ACPICA-event-handler-install-remove/20230701-023629
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
linux-next
patch link:
https://lore.kernel.org/r/20230630183344.891077-8-michal.wilczynski%40intel.com
patch subject: [PATCH v6 7/9] acpi/nfit: Move handler installing logic to driver
config: x86_64-allyesconfig
(https://download.01.org/0day-ci/archive/20230701/202307010426.iatkxynx-...@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce:
(https://download.01.org/0day-ci/archive/20230701/202307010426.iatkxynx-...@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/202307010426.iatkxynx-...@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/acpi/nfit/core.c:3294:6: warning: no previous prototype for
>> 'acpi_nfit_remove_notify_handler' [-Wmissing-prototypes]
3294 | void acpi_nfit_remove_notify_handler(void *data)
| ^~~
vim +/acpi_nfit_remove_notify_handler +3294 drivers/acpi/nfit/core.c
3293
> 3294 void acpi_nfit_remove_notify_handler(void *data)
3295 {
3296 struct acpi_device *adev = data;
3297
3298 acpi_dev_remove_notify_handler(adev,
3299 ACPI_DEVICE_NOTIFY,
3300 acpi_nfit_notify);
3301 }
3302
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Re: [PATCH] nvdimm: Avoid wasting some memory.
Hi Christophe,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on v6.0-rc3]
[also build test WARNING on linus/master next-20220901]
[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/Christophe-JAILLET/nvdimm-Avoid-wasting-some-memory/20220904-215140
base:b90cb1053190353cc30f0fef0ef1f378ccc063c5
config: x86_64-randconfig-a014
(https://download.01.org/0day-ci/archive/20220905/20220905.tai7tse5-...@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project
f28c006a5895fc0e329fe15fead81e37457cb1d1)
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/af94e709929390501b3d2f6e933fa0c1244a2029
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review
Christophe-JAILLET/nvdimm-Avoid-wasting-some-memory/20220904-215140
git checkout af94e709929390501b3d2f6e933fa0c1244a2029
# 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=x86_64 SHELL=/bin/bash drivers/nvdimm/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot
All warnings (new ones prefixed by >>):
>> drivers/nvdimm/btt_devs.c:335:6: warning: no previous prototype for function
>> 'nd_btt_free' [-Wmissing-prototypes]
void nd_btt_free(void *data)
^
drivers/nvdimm/btt_devs.c:335:1: note: declare 'static' if the function is
not intended to be used outside of this translation unit
void nd_btt_free(void *data)
^
static
1 warning generated.
vim +/nd_btt_free +335 drivers/nvdimm/btt_devs.c
334
> 335 void nd_btt_free(void *data)
336 {
337 kfree(data);
338 }
339
--
0-DAY CI Kernel Test Service
https://01.org/lkp
Re: [PATCH] dax: Fix potential uaf in __dax_pmem_probe()
Hi Jianglei,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.19-rc4 next-20220629]
[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/Jianglei-Nie/dax-Fix-potential-uaf-in-__dax_pmem_probe/20220629-152544
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
941e3e7912696b9fbe3586083a7c2e102cee7a87
config: x86_64-rhel-8.3
(https://download.01.org/0day-ci/archive/20220629/202206292354.bfjgfb0c-...@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
#
https://github.com/intel-lab-lkp/linux/commit/3b977a761f194fc61bdd0f6e97e1863ff32a04c5
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review
Jianglei-Nie/dax-Fix-potential-uaf-in-__dax_pmem_probe/20220629-152544
git checkout 3b977a761f194fc61bdd0f6e97e1863ff32a04c5
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/dax/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot
All error/warnings (new ones prefixed by >>):
drivers/dax/pmem.c: In function '__dax_pmem_probe':
>> drivers/dax/pmem.c:70:41: error: expected ')' before ';' token
70 | return ERR_PTR((dev_dax);
| ~ ^
| )
>> drivers/dax/pmem.c:70:32: warning: passing argument 1 of 'ERR_PTR' makes
>> integer from pointer without a cast [-Wint-conversion]
70 | return ERR_PTR((dev_dax);
|^
||
|struct dev_dax *
In file included from include/linux/container_of.h:6,
from include/linux/list.h:5,
from include/linux/preempt.h:11,
from include/linux/spinlock.h:55,
from include/linux/mmzone.h:8,
from include/linux/gfp.h:6,
from include/linux/mm.h:7,
from include/linux/memremap.h:5,
from drivers/dax/pmem.c:3:
include/linux/err.h:24:48: note: expected 'long int' but argument is of type
'struct dev_dax *'
24 | static inline void * __must_check ERR_PTR(long error)
| ~^
>> drivers/dax/pmem.c:75:24: error: expected ';' before '}' token
75 | return dev_dax;
|^
|;
76 | }
| ~
drivers/dax/pmem.c:76:1: error: control reaches end of non-void function
[-Werror=return-type]
76 | }
| ^
cc1: some warnings being treated as errors
vim +70 drivers/dax/pmem.c
9
10 static struct dev_dax *__dax_pmem_probe(struct device *dev)
11 {
12 struct range range;
13 int rc, id, region_id;
14 resource_size_t offset;
15 struct nd_pfn_sb *pfn_sb;
16 struct dev_dax *dev_dax;
17 struct dev_dax_data data;
18 struct nd_namespace_io *nsio;
19 struct dax_region *dax_region;
20 struct dev_pagemap pgmap = { };
21 struct nd_namespace_common *ndns;
22 struct nd_dax *nd_dax = to_nd_dax(dev);
23 struct nd_pfn *nd_pfn = _dax->nd_pfn;
24 struct nd_region *nd_region = to_nd_region(dev->parent);
25
26 ndns = nvdimm_namespace_common_probe(dev);
27 if (IS_ERR(ndns))
28 return ERR_CAST(ndns);
29
30 /* parse the 'pfn' info block via ->rw_bytes */
31 rc = devm_namespace_enable(dev, ndns, nd_info_block_reserve());
32 if (rc)
33 return ERR_PTR(rc);
34 rc = nvdimm_setup_pfn(nd_pfn, );
35 if (rc)
36 return ERR_PTR(rc);
37 devm_namespace_disable(dev, ndns);
38
39 /* reserve the metadata area, device-dax will reserve the data
*/
40 pfn_sb = nd_pfn->pfn_sb;
41 offset = le64_to_cpu(pfn_sb->dataoff);
42 nsio = to_nd_namespace_io(>dev);
43 if (!devm_request_mem_region(dev, nsio->res.start, offset,
44 dev_name(>dev))) {
45 dev_warn(dev, "could not reserve metadata\n");
46 return ERR_PTR(-EBUSY);
47 }
48
4
Re: [PATCH] device-dax: use kobj_to_dev()
Hi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.18-rc4 next-20220422]
[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/cgel-zte-gmail-com/device-dax-use-kobj_to_dev/20220425-185400
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
af2d861d4cd2a4da5137f795ee3509e6f944a25b
config: hexagon-randconfig-r041-20220425
(https://download.01.org/0day-ci/archive/20220426/202204260238.kdqglosu-...@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project
1cddcfdc3c683b393df1a5c9063252eb60e52818)
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/83eff180ded41da8e042373de81fa823835a1be0
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review
cgel-zte-gmail-com/device-dax-use-kobj_to_dev/20220425-185400
git checkout 83eff180ded41da8e042373de81fa823835a1be0
# 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/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot
All errors (new ones prefixed by >>):
>> drivers/dax/bus.c:515:40: error: expected ';' at end of declaration
struct device *dev = kobj_to_dev(kobj)
^
;
1 error generated.
vim +515 drivers/dax/bus.c
511
512 static umode_t dax_region_visible(struct kobject *kobj, struct
attribute *a,
513 int n)
514 {
> 515 struct device *dev = kobj_to_dev(kobj)
516 struct dax_region *dax_region = dev_get_drvdata(dev);
517
518 if (is_static(dax_region))
519 if (a == _attr_available_size.attr
520 || a == _attr_create.attr
521 || a == _attr_seed.attr
522 || a == _attr_delete.attr)
523 return 0;
524 return a->mode;
525 }
526
--
0-DAY CI Kernel Test Service
https://01.org/lkp
Re: [PATCH] device-dax: use kobj_to_dev()
Hi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.18-rc4 next-20220422]
[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/cgel-zte-gmail-com/device-dax-use-kobj_to_dev/20220425-185400
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
af2d861d4cd2a4da5137f795ee3509e6f944a25b
config: i386-randconfig-r016-20220425
(https://download.01.org/0day-ci/archive/20220426/202204260044.wlrouziw-...@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-20) 11.2.0
reproduce (this is a W=1 build):
#
https://github.com/intel-lab-lkp/linux/commit/83eff180ded41da8e042373de81fa823835a1be0
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review
cgel-zte-gmail-com/device-dax-use-kobj_to_dev/20220425-185400
git checkout 83eff180ded41da8e042373de81fa823835a1be0
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/dax/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot
All errors (new ones prefixed by >>):
drivers/dax/bus.c: In function 'dax_region_visible':
>> drivers/dax/bus.c:516:9: error: expected ',' or ';' before 'struct'
516 | struct dax_region *dax_region = dev_get_drvdata(dev);
| ^~
>> drivers/dax/bus.c:518:23: error: 'dax_region' undeclared (first use in this
>> function)
518 | if (is_static(dax_region))
| ^~
drivers/dax/bus.c:518:23: note: each undeclared identifier is reported only
once for each function it appears in
drivers/dax/bus.c:515:24: warning: unused variable 'dev' [-Wunused-variable]
515 | struct device *dev = kobj_to_dev(kobj)
|^~~
vim +516 drivers/dax/bus.c
0f3da14a4f0503 Dan Williams 2020-10-13 511
c2f3011ee697f8 Dan Williams 2020-10-13 512 static umode_t
dax_region_visible(struct kobject *kobj, struct attribute *a,
c2f3011ee697f8 Dan Williams 2020-10-13 513 int n)
c2f3011ee697f8 Dan Williams 2020-10-13 514 {
83eff180ded41d Minghao Chi 2022-04-25 515 struct device *dev =
kobj_to_dev(kobj)
c2f3011ee697f8 Dan Williams 2020-10-13 @516 struct dax_region *dax_region =
dev_get_drvdata(dev);
c2f3011ee697f8 Dan Williams 2020-10-13 517
0f3da14a4f0503 Dan Williams 2020-10-13 @518 if (is_static(dax_region))
0f3da14a4f0503 Dan Williams 2020-10-13 519 if (a ==
_attr_available_size.attr
0f3da14a4f0503 Dan Williams 2020-10-13 520 || a ==
_attr_create.attr
0f3da14a4f0503 Dan Williams 2020-10-13 521 || a ==
_attr_seed.attr
0f3da14a4f0503 Dan Williams 2020-10-13 522 || a ==
_attr_delete.attr)
c2f3011ee697f8 Dan Williams 2020-10-13 523 return 0;
c2f3011ee697f8 Dan Williams 2020-10-13 524 return a->mode;
c2f3011ee697f8 Dan Williams 2020-10-13 525 }
c2f3011ee697f8 Dan Williams 2020-10-13 526
--
0-DAY CI Kernel Test Service
https://01.org/lkp
Re: [PATCH v12 6/7] xfs: Implement ->notify_failure() for XFS
Hi Shiyang, Thank you for the patch! Yet something to improve: [auto build test ERROR on hnaz-mm/master] [also build test ERROR on next-20220408] [cannot apply to xfs-linux/for-next linus/master linux/master v5.18-rc1] [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/Shiyang-Ruan/fsdax-introduce-fs-query-to-support-reflink/20220411-001048 base: https://github.com/hnaz/linux-mm master config: s390-allyesconfig (https://download.01.org/0day-ci/archive/20220411/202204110700.66eh1xzg-...@intel.com/config) compiler: s390-linux-gcc (GCC) 11.2.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/bf68be0c39b8ecc4223b948a9ee126af167d74f0 git remote add linux-review https://github.com/intel-lab-lkp/linux git fetch --no-tags linux-review Shiyang-Ruan/fsdax-introduce-fs-query-to-support-reflink/20220411-001048 git checkout bf68be0c39b8ecc4223b948a9ee126af167d74f0 # save the config file to linux build tree mkdir build_dir COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=s390 SHELL=/bin/bash If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot All errors (new ones prefixed by >>): s390-linux-ld: fs/xfs/xfs_buf.o: in function `xfs_alloc_buftarg': >> xfs_buf.c:(.text+0x9920): undefined reference to `xfs_dax_holder_operations' -- 0-DAY CI Kernel Test Service https://01.org/lkp
Re: [PATCH v12 2/7] mm: factor helpers for memory_failure_dev_pagemap
Hi Shiyang,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on hnaz-mm/master]
[also build test WARNING on next-20220408]
[cannot apply to xfs-linux/for-next linus/master linux/master v5.18-rc1]
[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/Shiyang-Ruan/fsdax-introduce-fs-query-to-support-reflink/20220411-001048
base: https://github.com/hnaz/linux-mm master
config: x86_64-randconfig-a011
(https://download.01.org/0day-ci/archive/20220411/202204110420.o844czyb-...@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-19) 11.2.0
reproduce (this is a W=1 build):
#
https://github.com/intel-lab-lkp/linux/commit/9ab00d3f6d4d9d3d2e4446480567af17c8726bd2
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review
Shiyang-Ruan/fsdax-introduce-fs-query-to-support-reflink/20220411-001048
git checkout 9ab00d3f6d4d9d3d2e4446480567af17c8726bd2
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot
All warnings (new ones prefixed by >>):
mm/memory-failure.c: In function 'mf_generic_kill_procs':
>> mm/memory-failure.c:1533:13: warning: variable 'rc' set but not used
>> [-Wunused-but-set-variable]
1533 | int rc = 0;
| ^~
vim +/rc +1533 mm/memory-failure.c
1526
1527 static int mf_generic_kill_procs(unsigned long long pfn, int flags,
1528 struct dev_pagemap *pgmap)
1529 {
1530 struct page *page = pfn_to_page(pfn);
1531 LIST_HEAD(to_kill);
1532 dax_entry_t cookie;
> 1533 int rc = 0;
1534
1535 /*
1536 * Pages instantiated by device-dax (not filesystem-dax)
1537 * may be compound pages.
1538 */
1539 page = compound_head(page);
1540
1541 /*
1542 * Prevent the inode from being freed while we are interrogating
1543 * the address_space, typically this would be handled by
1544 * lock_page(), but dax pages do not use the page lock. This
1545 * also prevents changes to the mapping of this pfn until
1546 * poison signaling is complete.
1547 */
1548 cookie = dax_lock_page(page);
1549 if (!cookie)
1550 return -EBUSY;
1551
1552 if (hwpoison_filter(page)) {
1553 rc = -EOPNOTSUPP;
1554 goto unlock;
1555 }
1556
1557 if (pgmap->type == MEMORY_DEVICE_PRIVATE) {
1558 /*
1559 * TODO: Handle HMM pages which may need coordination
1560 * with device-side memory.
1561 */
1562 return -EBUSY;
1563 }
1564
1565 /*
1566 * Use this flag as an indication that the dax page has been
1567 * remapped UC to prevent speculative consumption of poison.
1568 */
1569 SetPageHWPoison(page);
1570
1571 /*
1572 * Unlike System-RAM there is no possibility to swap in a
1573 * different physical page at a given virtual address, so all
1574 * userspace consumption of ZONE_DEVICE memory necessitates
1575 * SIGBUS (i.e. MF_MUST_KILL)
1576 */
1577 flags |= MF_ACTION_REQUIRED | MF_MUST_KILL;
1578 collect_procs(page, _kill, true);
1579
1580 unmap_and_kill(_kill, pfn, page->mapping, page->index,
flags);
1581 unlock:
1582 dax_unlock_page(page, cookie);
1583 return 0;
1584 }
1585
--
0-DAY CI Kernel Test Service
https://01.org/lkp
Re: [PATCH v12 2/7] mm: factor helpers for memory_failure_dev_pagemap
Hi Shiyang,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on hnaz-mm/master]
[also build test WARNING on next-20220408]
[cannot apply to xfs-linux/for-next linus/master linux/master v5.18-rc1]
[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/Shiyang-Ruan/fsdax-introduce-fs-query-to-support-reflink/20220411-001048
base: https://github.com/hnaz/linux-mm master
config: arm64-randconfig-r021-20220410
(https://download.01.org/0day-ci/archive/20220411/202204110348.fupyvjk7-...@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project
256c6b0ba14e8a7ab6373b61b7193ea8c0a3651c)
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
# install arm64 cross compiling tool for clang build
# apt-get install binutils-aarch64-linux-gnu
#
https://github.com/intel-lab-lkp/linux/commit/9ab00d3f6d4d9d3d2e4446480567af17c8726bd2
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review
Shiyang-Ruan/fsdax-introduce-fs-query-to-support-reflink/20220411-001048
git checkout 9ab00d3f6d4d9d3d2e4446480567af17c8726bd2
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1
O=build_dir ARCH=arm64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot
All warnings (new ones prefixed by >>):
>> mm/memory-failure.c:1533:6: warning: variable 'rc' set but not used
>> [-Wunused-but-set-variable]
int rc = 0;
^
1 warning generated.
vim +/rc +1533 mm/memory-failure.c
1526
1527 static int mf_generic_kill_procs(unsigned long long pfn, int flags,
1528 struct dev_pagemap *pgmap)
1529 {
1530 struct page *page = pfn_to_page(pfn);
1531 LIST_HEAD(to_kill);
1532 dax_entry_t cookie;
> 1533 int rc = 0;
1534
1535 /*
1536 * Pages instantiated by device-dax (not filesystem-dax)
1537 * may be compound pages.
1538 */
1539 page = compound_head(page);
1540
1541 /*
1542 * Prevent the inode from being freed while we are interrogating
1543 * the address_space, typically this would be handled by
1544 * lock_page(), but dax pages do not use the page lock. This
1545 * also prevents changes to the mapping of this pfn until
1546 * poison signaling is complete.
1547 */
1548 cookie = dax_lock_page(page);
1549 if (!cookie)
1550 return -EBUSY;
1551
1552 if (hwpoison_filter(page)) {
1553 rc = -EOPNOTSUPP;
1554 goto unlock;
1555 }
1556
1557 if (pgmap->type == MEMORY_DEVICE_PRIVATE) {
1558 /*
1559 * TODO: Handle HMM pages which may need coordination
1560 * with device-side memory.
1561 */
1562 return -EBUSY;
1563 }
1564
1565 /*
1566 * Use this flag as an indication that the dax page has been
1567 * remapped UC to prevent speculative consumption of poison.
1568 */
1569 SetPageHWPoison(page);
1570
1571 /*
1572 * Unlike System-RAM there is no possibility to swap in a
1573 * different physical page at a given virtual address, so all
1574 * userspace consumption of ZONE_DEVICE memory necessitates
1575 * SIGBUS (i.e. MF_MUST_KILL)
1576 */
1577 flags |= MF_ACTION_REQUIRED | MF_MUST_KILL;
1578 collect_procs(page, _kill, true);
1579
1580 unmap_and_kill(_kill, pfn, page->mapping, page->index,
flags);
1581 unlock:
1582 dax_unlock_page(page, cookie);
1583 return 0;
1584 }
1585
--
0-DAY CI Kernel Test Service
https://01.org/lkp
Re: [PATCH v12 6/7] xfs: Implement ->notify_failure() for XFS
Hi Shiyang,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on hnaz-mm/master]
[also build test ERROR on next-20220408]
[cannot apply to xfs-linux/for-next linus/master linux/master v5.18-rc1]
[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/Shiyang-Ruan/fsdax-introduce-fs-query-to-support-reflink/20220411-001048
base: https://github.com/hnaz/linux-mm master
config: s390-defconfig
(https://download.01.org/0day-ci/archive/20220411/202204110240.oa3g7lsw-...@intel.com/config)
compiler: s390-linux-gcc (GCC) 11.2.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/bf68be0c39b8ecc4223b948a9ee126af167d74f0
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review
Shiyang-Ruan/fsdax-introduce-fs-query-to-support-reflink/20220411-001048
git checkout bf68be0c39b8ecc4223b948a9ee126af167d74f0
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross
O=build_dir ARCH=s390 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot
All errors (new ones prefixed by >>):
s390-linux-ld: fs/xfs/xfs_buf.o: in function `xfs_alloc_buftarg':
>> fs/xfs/xfs_buf.c:1968: undefined reference to `xfs_dax_holder_operations'
pahole: .tmp_vmlinux.btf: No such file or directory
.btf.vmlinux.bin.o: file not recognized: file format not recognized
vim +1968 fs/xfs/xfs_buf.c
1955
1956 struct xfs_buftarg *
1957 xfs_alloc_buftarg(
1958 struct xfs_mount*mp,
1959 struct block_device *bdev)
1960 {
1961 xfs_buftarg_t *btp;
1962
1963 btp = kmem_zalloc(sizeof(*btp), KM_NOFS);
1964
1965 btp->bt_mount = mp;
1966 btp->bt_dev = bdev->bd_dev;
1967 btp->bt_bdev = bdev;
> 1968 btp->bt_daxdev = fs_dax_get_by_bdev(bdev,
> >bt_dax_part_off, mp,
1969 _dax_holder_operations);
1970
1971 /*
1972 * Buffer IO error rate limiting. Limit it to no more than 10
messages
1973 * per 30 seconds so as to not spam logs too much on repeated
errors.
1974 */
1975 ratelimit_state_init(>bt_ioerror_rl, 30 * HZ,
1976 DEFAULT_RATELIMIT_BURST);
1977
1978 if (xfs_setsize_buftarg_early(btp, bdev))
1979 goto error_free;
1980
1981 if (list_lru_init(>bt_lru))
1982 goto error_free;
1983
1984 if (percpu_counter_init(>bt_io_count, 0, GFP_KERNEL))
1985 goto error_lru;
1986
1987 btp->bt_shrinker.count_objects = xfs_buftarg_shrink_count;
1988 btp->bt_shrinker.scan_objects = xfs_buftarg_shrink_scan;
1989 btp->bt_shrinker.seeks = DEFAULT_SEEKS;
1990 btp->bt_shrinker.flags = SHRINKER_NUMA_AWARE;
1991 if (register_shrinker(>bt_shrinker))
1992 goto error_pcpu;
1993 return btp;
1994
1995 error_pcpu:
1996 percpu_counter_destroy(>bt_io_count);
1997 error_lru:
1998 list_lru_destroy(>bt_lru);
1999 error_free:
2000 kmem_free(btp);
2001 return NULL;
2002 }
2003
--
0-DAY CI Kernel Test Service
https://01.org/lkp
