[lkp-robot] [rhashtable] 60be2ebf32: INFO:suspicious_RCU_usage

2017-02-08 Thread kernel test robot
FYI, we noticed the following commit: commit: 60be2ebf326aa90c88e9a967412557d832a1612e ("rhashtable: Add nested tables") url: https://github.com/0day-ci/linux/commits/Herbert-Xu/rhashtable-Handle-table-allocation-failure-during-insertion/20170207-204835 in testcase: boot on test machine: qem

[lkp-robot] [xdp] 543d41bf78: INFO:suspicious_RCU_usage

2017-02-12 Thread kernel test robot
FYI, we noticed the following commit: commit: 543d41bf78792e858e6f6598945d307ff808b7fc ("xdp: Infrastructure to generalize XDP") url: https://github.com/0day-ci/linux/commits/Tom-Herbert/xdp-Generalize-XDP/20170209-092238 in testcase: trinity with following parameters: runtime: 300s

[lkp-robot] [rhashtable ] df7008bdd5: Kernel_panic-not_syncing:rtnetlink_init:cannot_initialize_rtnetlink

2017-04-27 Thread kernel test robot
FYI, we noticed the following commit: commit: df7008bdd52176211797a90420f40d5d2d2b90c2 ("rhashtable - Cap total number of entries to 2^31") url: https://github.com/0day-ci/linux/commits/Herbert-Xu/rhashtable-Cap-total-number-of-entries-to-2-31/20170428-021447 in testcase: boot on test machin

[rhashtable] 6d684e5469: Kernel panic - not syncing: rtnetlink_init: cannot initialize rtnetlink

2017-04-27 Thread kernel test robot
Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master commit 6d684e54690caef45cf14051ddeb7c71beeb681b Author: Herbert Xu AuthorDate: Thu Apr 27 13:44:51 2017 +0800 Commit: David S. M

[lkp] [net] 70a8118a03: BUG: workqueue leaked lock or atomic: kworker/0:1/0x00000000/28

2016-09-16 Thread kernel test robot
FYI, we noticed the following commit: https://github.com/0day-ci/linux Christophe-JAILLET/net-inet-diag-Fix-an-error-handling/20160912-140503 commit 70a8118a03243de2aba508d79cc1a042db094191 ("net: inet: diag: Fix an error handling") in testcase: boot on test machine: qemu-system-x86_64 -enabl

[lkp] [netfilter] 68263ddb47: WARNING: CPU: 0 PID: 1225 at net/netfilter/nf_conntrack_seqadj.c:232 nf_ct_seq_offset+0x7a/0x9a

2016-09-16 Thread kernel test robot
FYI, we noticed the following commit: https://github.com/0day-ci/linux fgao-ikuai8-com/netfilter-seqadj-Fix-some-possible-panics-of-seqadj-when-mem-is-exhausted/20160902-095727 commit 68263ddb4777cc996868498e3d56f616851966d2 ("netfilter: seqadj: Fix some possible panics of seqadj when mem is ex

[lkp] [net] 50d4a9ef15: INFO:suspicious_RCU_usage

2016-11-22 Thread kernel test robot
FYI, we noticed the following commit: commit 50d4a9ef15cee93344653f6ca8f9bab62e76e972 ("net: ipv6: avoid errors due to per-cpu atomic alloc") url: https://github.com/0day-ci/linux/commits/Mike-Manning/net-ipv6-avoid-errors-due-to-per-cpu-atomic-alloc/20161122-202055 in testcase: trinity with

[lkp] [net] af1fee9821: BUG:spinlock_trylock_failure_on_UP_on_CPU

2016-11-06 Thread kernel test robot
FYI, we noticed the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master commit af1fee98219992ba2c12441a447719652ed7e983 ("net: phy: Add support for Microsemi VSC 8530/40 Fast Ethernet PHY") in testcase: boot on test machine: qemu-system-x86_64 -enable-kv

[lkp] [net/netpolicy] 19e7d15d66: EIP: [] netpolicy_unregister+0x23a/0x28a SS:ESP 0068:ceb19d94

2016-08-16 Thread kernel test robot
FYI, we noticed the following commit: https://github.com/0day-ci/linux kan-liang-intel-com/net-introduce-NET-policy/20160805-034810 commit 19e7d15d66de8b17e3f2706b786fdc36932bbdbb ("net/netpolicy: limit the total record number") in testcase: boot on test machine: 2 threads qemu-system-i386 -e

Re: [PATCH net-next v2 05/13] virtio_ring: introduce add api for premapped

2024-10-30 Thread kernel test robot
Hi Xuan, 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/Xuan-Zhuo/virtio_ring-introduce-vring_need_unmap_buffer/20241030-162739 base: net-next/main patch link: https

[mst-vhost:vhost 29/35] drivers/virtio/virtio_ring.c:2103:22: sparse: sparse: symbol 'packed_ops' was not declared. Should it be static?

2025-05-19 Thread kernel test robot
/commit), kindly add following tags | Reported-by: kernel test robot | Closes: https://lore.kernel.org/oe-kbuild-all/202505200015.m6vjylry-...@intel.com/ sparse warnings: (new ones prefixed by >>) >> drivers/virtio/virtio_ring.c:2103:22: sparse: sparse: symbol 'packed_ops' >&

[mst-vhost:vhost 35/35] drivers/virtio/virtio_ring.c:1281:22: sparse: sparse: symbol 'split_in_order_ops' was not declared. Should it be static?

2025-05-19 Thread kernel test robot
), kindly add following tags | Reported-by: kernel test robot | Closes: https://lore.kernel.org/oe-kbuild-all/202505200227.usdch63w-...@intel.com/ sparse warnings: (new ones prefixed by >>) >> drivers/virtio/virtio_ring.c:1281:22: sparse: sparse: symbol >> 'split_in_orde

[mst-vhost:vhost 4/8] include/linux/pci.h:2738:7: error: call to undeclared function 'pci_device_is_present'; ISO C99 and later do not support implicit function declarations

2025-07-09 Thread kernel test robot
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/202507091645.apgujh6x-...@intel.com/ All errors (new ones prefixed by >>): In file include

[mst-vhost:vhost 4/8] include/linux/pci.h:2738:14: warning: implicit declaration of function 'pci_device_is_present'; did you mean 'pci_dev_present'?

2025-07-09 Thread kernel test robot
. 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/202507091726.qksmdnk7-...@intel.com/ All warnings (new ones prefixed by >>): In file included from drivers/firmware/efi/libstub/pc

<    2   3   4   5   6   7