- Linux-stable-mirror - lists.linaro.org

[PATCH 01/20] can: raw: check for CAN FD capable netdev in raw_sendmsg()

by Marc Kleine-Budde

From: Oliver Hartkopp <socketcan(a)hartkopp.net> When the socket is CAN FD enabled it can handle CAN FD frame transmissions. Add an additional check in raw_sendmsg() as a CAN2.0 CAN driver (non CAN FD) should never see a CAN FD frame. Due to the commonly used can_dropped_invalid_skb() function the CAN 2.0 driver would drop that CAN FD frame anyway - but with this patch the user gets a proper -EINVAL return code. Signed-off-by: Oliver Hartkopp <socketcan(a)hartkopp.net> Cc: linux-stable <stable(a)vger.kernel.org> Signed-off-by: Marc Kleine-Budde <mkl(a)pengutronix.de> --- net/can/raw.c | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/net/can/raw.c b/net/can/raw.c index 1051eee82581..3aab7664933f 100644 --- a/net/can/raw.c +++ b/net/can/raw.c @@ -745,18 +745,19 @@ static int raw_sendmsg(struct socket *sock, struct msghdr *msg, size_t size) } else ifindex = ro->ifindex; - if (ro->fd_frames) { + dev = dev_get_by_index(sock_net(sk), ifindex); + if (!dev) + return -ENXIO; + + err = -EINVAL; + if (ro->fd_frames && dev->mtu == CANFD_MTU) { if (unlikely(size != CANFD_MTU && size != CAN_MTU)) - return -EINVAL; + goto put_dev; } else { if (unlikely(size != CAN_MTU)) - return -EINVAL; + goto put_dev; } - dev = dev_get_by_index(sock_net(sk), ifindex); - if (!dev) - return -ENXIO; - skb = sock_alloc_send_skb(sk, size + sizeof(struct can_skb_priv), msg->msg_flags & MSG_DONTWAIT, &err); if (!skb) -- 2.19.1

6 years, 9 months

1
0
0 0

[PATCH AUTOSEL 4.9 01/48] net: ethernet: ti: cpsw: unsync mcast entries while switch promisc mode

by Sasha Levin

From: Ivan Khoronzhuk <ivan.khoronzhuk(a)linaro.org> [ Upstream commit 9737cc99dd14b5b8b9d267618a6061feade8ea68 ] After flushing all mcast entries from the table, the ones contained in mc list of ndev are not restored when promisc mode is toggled off, because they are considered as synched with ALE, thus, in order to restore them after promisc mode - reset syncing info. This fix touches only switch mode devices, including single port boards like Beagle Bone. Fixes: commit 5da1948969bc ("net: ethernet: ti: cpsw: fix lost of mcast packets while rx_mode update") Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk(a)linaro.org> Reviewed-by: Grygorii Strashko <grygorii.strashko(a)ti.com> Signed-off-by: David S. Miller <davem(a)davemloft.net> Signed-off-by: Sasha Levin <sashal(a)kernel.org> --- drivers/net/ethernet/ti/cpsw.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/ethernet/ti/cpsw.c b/drivers/net/ethernet/ti/cpsw.c index d7cb205fe7e2..892b06852e15 100644 --- a/drivers/net/ethernet/ti/cpsw.c +++ b/drivers/net/ethernet/ti/cpsw.c @@ -590,6 +590,7 @@ static void cpsw_set_promiscious(struct net_device *ndev, bool enable) /* Clear all mcast from ALE */ cpsw_ale_flush_multicast(ale, ALE_ALL_PORTS, -1); + __dev_mc_unsync(ndev, NULL); /* Flood All Unicast Packets to Host port */ cpsw_ale_control_set(ale, 0, ALE_P0_UNI_FLOOD, 1); -- 2.17.1

6 years, 9 months

2
48
0 0

[PATCH] kmemleak: Turn kmemleak_lock to raw spinlock on RT

by zhe.he＠windriver.com

From: He Zhe <zhe.he(a)windriver.com> kmemleak_lock, as a rwlock on RT, can possibly be held in atomic context and causes the follow BUG. BUG: scheduling while atomic: migration/15/132/0x00000002 Modules linked in: iTCO_wdt iTCO_vendor_support intel_rapl pcc_cpufreq pnd2_edac intel_powerclamp coretemp crct10dif_pclmul crct10dif_common aesni_intel matroxfb_base aes_x86_64 matroxfb_g450 matroxfb_accel crypto_simd matroxfb_DAC1064 cryptd glue_helper g450_pll matroxfb_misc i2c_ismt i2c_i801 acpi_cpufreq Preemption disabled at: [<ffffffff8c927c11>] cpu_stopper_thread+0x71/0x100 CPU: 15 PID: 132 Comm: migration/15 Not tainted 4.19.0-rt1-preempt-rt #1 Hardware name: Intel Corp. Harcuvar/Server, BIOS HAVLCRB1.X64.0015.D62.1708310404 08/31/2017 Call Trace: dump_stack+0x4f/0x6a ? cpu_stopper_thread+0x71/0x100 __schedule_bug.cold.16+0x38/0x55 __schedule+0x484/0x6c0 schedule+0x3d/0xe0 rt_spin_lock_slowlock_locked+0x118/0x2a0 rt_spin_lock_slowlock+0x57/0x90 __rt_spin_lock+0x26/0x30 __write_rt_lock+0x23/0x1a0 ? intel_pmu_cpu_dying+0x67/0x70 rt_write_lock+0x2a/0x30 find_and_remove_object+0x1e/0x80 delete_object_full+0x10/0x20 kmemleak_free+0x32/0x50 kfree+0x104/0x1f0 ? x86_pmu_starting_cpu+0x30/0x30 intel_pmu_cpu_dying+0x67/0x70 x86_pmu_dying_cpu+0x1a/0x30 cpuhp_invoke_callback+0x92/0x700 take_cpu_down+0x70/0xa0 multi_cpu_stop+0x62/0xc0 ? cpu_stop_queue_work+0x130/0x130 cpu_stopper_thread+0x79/0x100 smpboot_thread_fn+0x20f/0x2d0 kthread+0x121/0x140 ? sort_range+0x30/0x30 ? kthread_park+0x90/0x90 ret_from_fork+0x35/0x40 And on v4.18 stable tree the following call trace, caused by grabbing kmemleak_lock again, is also observed. kernel BUG at kernel/locking/rtmutex.c:1048! invalid opcode: 0000 [#1] PREEMPT SMP PTI CPU: 5 PID: 689 Comm: mkfs.ext4 Not tainted 4.18.16-rt9-preempt-rt #1 Hardware name: Intel Corp. Harcuvar/Server, BIOS HAVLCRB1.X64.0015.D62.1708310404 08/31/2017 RIP: 0010:rt_spin_lock_slowlock_locked+0x277/0x2a0 Code: e8 5e 64 61 ff e9 bc fe ff ff e8 54 64 61 ff e9 b7 fe ff ff 0f 0b e8 98 57 53 ff e9 43 fe ff ff e8 8e 57 53 ff e9 74 ff ff ff <0f> 0b 0f 0b 0f 0b 48 8b 43 10 48 85 c0 74 06 48 3b 58 38 75 0b 49 RSP: 0018:ffff936846d4f3b0 EFLAGS: 00010046 RAX: ffff8e3680361e00 RBX: ffffffff83a8b240 RCX: 0000000000000001 RDX: 0000000000000000 RSI: ffff8e3680361e00 RDI: ffffffff83a8b258 RBP: ffff936846d4f3e8 R08: ffff8e3680361e01 R09: ffffffff82adfdf0 R10: ffffffff827ede18 R11: 0000000000000000 R12: ffff936846d4f3f8 R13: ffff8e3680361e00 R14: ffff936846d4f3f8 R15: 0000000000000246 FS: 00007fc8b6bfd780(0000) GS:ffff8e369f340000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000055fb5659e000 CR3: 00000007fdd14000 CR4: 00000000003406e0 Call Trace: ? preempt_count_add+0x74/0xc0 rt_spin_lock_slowlock+0x57/0x90 ? __kernel_text_address+0x12/0x40 ? __save_stack_trace+0x75/0x100 __rt_spin_lock+0x26/0x30 __write_rt_lock+0x23/0x1a0 rt_write_lock+0x2a/0x30 create_object+0x17d/0x2b0 kmemleak_alloc+0x34/0x50 kmem_cache_alloc+0x146/0x220 ? mempool_alloc_slab+0x15/0x20 mempool_alloc_slab+0x15/0x20 mempool_alloc+0x65/0x170 sg_pool_alloc+0x21/0x60 __sg_alloc_table+0x101/0x160 ? sg_free_table_chained+0x30/0x30 sg_alloc_table_chained+0x8b/0xb0 scsi_init_sgtable+0x31/0x90 scsi_init_io+0x44/0x130 sd_setup_write_same16_cmnd+0xef/0x150 sd_init_command+0x6bf/0xaa0 ? cgroup_base_stat_cputime_account_end.isra.0+0x26/0x60 ? elv_rb_del+0x2a/0x40 scsi_setup_cmnd+0x8e/0x140 scsi_prep_fn+0x5d/0x140 blk_peek_request+0xda/0x2f0 scsi_request_fn+0x33/0x550 ? cfq_rb_erase+0x23/0x40 __blk_run_queue+0x43/0x60 cfq_insert_request+0x2f3/0x5d0 __elv_add_request+0x160/0x290 blk_flush_plug_list+0x204/0x230 schedule+0x87/0xe0 __write_rt_lock+0x18b/0x1a0 rt_write_lock+0x2a/0x30 create_object+0x17d/0x2b0 kmemleak_alloc+0x34/0x50 __kmalloc_node+0x1cd/0x340 alloc_request_size+0x30/0x70 mempool_alloc+0x65/0x170 ? ioc_lookup_icq+0x54/0x70 get_request+0x4e3/0x8d0 ? wait_woken+0x80/0x80 blk_queue_bio+0x153/0x470 generic_make_request+0x1dc/0x3f0 submit_bio+0x49/0x140 ? next_bio+0x38/0x40 submit_bio_wait+0x59/0x90 blkdev_issue_discard+0x7a/0xd0 ? _raw_spin_unlock_irqrestore+0x18/0x50 blk_ioctl_discard+0xc7/0x110 blkdev_ioctl+0x57e/0x960 ? __wake_up+0x13/0x20 block_ioctl+0x3d/0x50 do_vfs_ioctl+0xa8/0x610 ? vfs_write+0x166/0x1b0 ksys_ioctl+0x67/0x90 __x64_sys_ioctl+0x1a/0x20 do_syscall_64+0x4d/0xf0 entry_SYSCALL_64_after_hwframe+0x44/0xa9 kmemleak is an error detecting feature. We would not expect as good performance as without it. As there is no raw rwlock defining helpers, we turn kmemleak_lock to a raw spinlock. Signed-off-by: He Zhe <zhe.he(a)windriver.com> Cc: stable(a)vger.kernel.org Cc: catalin.marinas(a)arm.com Cc: bigeasy(a)linutronix.de Cc: tglx(a)linutronix.de Cc: rostedt(a)goodmis.org --- mm/kmemleak.c | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/mm/kmemleak.c b/mm/kmemleak.c index 17dd883..b68a3d0 100644 --- a/mm/kmemleak.c +++ b/mm/kmemleak.c @@ -26,7 +26,7 @@ * * The following locks and mutexes are used by kmemleak: * - * - kmemleak_lock (rwlock): protects the object_list modifications and + * - kmemleak_lock (raw spinlock): protects the object_list modifications and * accesses to the object_tree_root. The object_list is the main list * holding the metadata (struct kmemleak_object) for the allocated memory * blocks. The object_tree_root is a red black tree used to look-up @@ -197,7 +197,7 @@ static LIST_HEAD(gray_list); /* search tree for object boundaries */ static struct rb_root object_tree_root = RB_ROOT; /* rw_lock protecting the access to object_list and object_tree_root */ -static DEFINE_RWLOCK(kmemleak_lock); +static DEFINE_RAW_SPINLOCK(kmemleak_lock); /* allocation caches for kmemleak internal data */ static struct kmem_cache *object_cache; @@ -491,9 +491,9 @@ static struct kmemleak_object *find_and_get_object(unsigned long ptr, int alias) struct kmemleak_object *object; rcu_read_lock(); - read_lock_irqsave(&kmemleak_lock, flags); + raw_spin_lock_irqsave(&kmemleak_lock, flags); object = lookup_object(ptr, alias); - read_unlock_irqrestore(&kmemleak_lock, flags); + raw_spin_unlock_irqrestore(&kmemleak_lock, flags); /* check whether the object is still available */ if (object && !get_object(object)) @@ -513,13 +513,13 @@ static struct kmemleak_object *find_and_remove_object(unsigned long ptr, int ali unsigned long flags; struct kmemleak_object *object; - write_lock_irqsave(&kmemleak_lock, flags); + raw_spin_lock_irqsave(&kmemleak_lock, flags); object = lookup_object(ptr, alias); if (object) { rb_erase(&object->rb_node, &object_tree_root); list_del_rcu(&object->object_list); } - write_unlock_irqrestore(&kmemleak_lock, flags); + raw_spin_unlock_irqrestore(&kmemleak_lock, flags); return object; } @@ -593,7 +593,7 @@ static struct kmemleak_object *create_object(unsigned long ptr, size_t size, /* kernel backtrace */ object->trace_len = __save_stack_trace(object->trace); - write_lock_irqsave(&kmemleak_lock, flags); + raw_spin_lock_irqsave(&kmemleak_lock, flags); min_addr = min(min_addr, ptr); max_addr = max(max_addr, ptr + size); @@ -624,7 +624,7 @@ static struct kmemleak_object *create_object(unsigned long ptr, size_t size, list_add_tail_rcu(&object->object_list, &object_list); out: - write_unlock_irqrestore(&kmemleak_lock, flags); + raw_spin_unlock_irqrestore(&kmemleak_lock, flags); return object; } @@ -1310,7 +1310,7 @@ static void scan_block(void *_start, void *_end, unsigned long *end = _end - (BYTES_PER_POINTER - 1); unsigned long flags; - read_lock_irqsave(&kmemleak_lock, flags); + raw_spin_lock_irqsave(&kmemleak_lock, flags); for (ptr = start; ptr < end; ptr++) { struct kmemleak_object *object; unsigned long pointer; @@ -1367,7 +1367,7 @@ static void scan_block(void *_start, void *_end, spin_unlock(&object->lock); } } - read_unlock_irqrestore(&kmemleak_lock, flags); + raw_spin_unlock_irqrestore(&kmemleak_lock, flags); } /* -- 2.7.4

6 years, 9 months

1
0
0 0

[PATCH v2 5/5] iwlwifi: mvm: don't use SAR Geo if basic SAR is not used

by Luca Coelho

From: Luca Coelho <luciano.coelho(a)intel.com> We can't use SAR Geo if basic SAR is not enabled, since the SAR Geo tables define offsets in relation to the basic SAR table in use. To fix this, make iwl_mvm_sar_init() return one in case WRDS is not available, so we can skip reading WGDS entirely. Fixes: a6bff3cb19b7 ("iwlwifi: mvm: add GEO_TX_POWER_LIMIT cmd for geographic tx power table") Cc: stable(a)vger.kernel.org # 4.12+ Signed-off-by: Luca Coelho <luciano.coelho(a)intel.com> --- In v2: * fix compilation when CONFIG_ACPI is not set; drivers/net/wireless/intel/iwlwifi/mvm/fw.c | 36 ++++++++++++++++----- 1 file changed, 28 insertions(+), 8 deletions(-) diff --git a/drivers/net/wireless/intel/iwlwifi/mvm/fw.c b/drivers/net/wireless/intel/iwlwifi/mvm/fw.c index 899f4a6432fb..2ba890445c35 100644 --- a/drivers/net/wireless/intel/iwlwifi/mvm/fw.c +++ b/drivers/net/wireless/intel/iwlwifi/mvm/fw.c @@ -928,6 +928,11 @@ static int iwl_mvm_sar_get_ewrd_table(struct iwl_mvm *mvm) return -ENOENT; } +static int iwl_mvm_sar_get_wgds_table(struct iwl_mvm *mvm) +{ + return -ENOENT; +} + static int iwl_mvm_sar_geo_init(struct iwl_mvm *mvm) { return 0; @@ -954,8 +959,11 @@ static int iwl_mvm_sar_init(struct iwl_mvm *mvm) IWL_DEBUG_RADIO(mvm, "WRDS SAR BIOS table invalid or unavailable. (%d)\n", ret); - /* if not available, don't fail and don't bother with EWRD */ - return 0; + /* + * If not available, don't fail and don't bother with EWRD. + * Return 1 to tell that we can't use WGDS either. + */ + return 1; } ret = iwl_mvm_sar_get_ewrd_table(mvm); @@ -968,9 +976,13 @@ static int iwl_mvm_sar_init(struct iwl_mvm *mvm) /* choose profile 1 (WRDS) as default for both chains */ ret = iwl_mvm_sar_select_profile(mvm, 1, 1); - /* if we don't have profile 0 from BIOS, just skip it */ + /* + * If we don't have profile 0 from BIOS, just skip it. This + * means that SAR Geo will not be enabled either, even if we + * have other valid profiles. + */ if (ret == -ENOENT) - return 0; + return 1; return ret; } @@ -1168,11 +1180,19 @@ int iwl_mvm_up(struct iwl_mvm *mvm) iwl_mvm_unref(mvm, IWL_MVM_REF_UCODE_DOWN); ret = iwl_mvm_sar_init(mvm); - if (ret) - goto error; + if (ret == 0) { + ret = iwl_mvm_sar_geo_init(mvm); + } else if (ret > 0 && !iwl_mvm_sar_get_wgds_table(mvm)) { + /* + * If basic SAR is not available, we check for WGDS, + * which should *not* be available either. If it is + * available, issue an error, because we can't use SAR + * Geo without basic SAR. + */ + IWL_ERR(mvm, "BIOS contains WGDS but no WRDS\n"); + } - ret = iwl_mvm_sar_geo_init(mvm); - if (ret) + if (ret < 0) goto error; iwl_mvm_leds_sync(mvm); -- 2.19.1

6 years, 9 months

1
0
0 0

Inquiry 12.11.18

by Daniel Murray

Hi,friend, This is Daniel Murray and i am from Sinara Group Co.Ltd Group Co.,LTD in Russia. We are glad to know about your company from the web and we are interested in your products. Could you kindly send us your Latest catalog and price list for our trial order. Best Regards, Daniel Murray Purchasing Manager

6 years, 9 months

1
0
0 0

stable-rc/linux-4.14.y boot: 94 boots: 4 failed, 66 passed with 16 offline, 8 conflicts (v4.14.80-223-g8ea94372bf00)

by kernelci.org bot

stable-rc/linux-4.14.y boot: 94 boots: 4 failed, 66 passed with 16 offline, 8 conflicts (v4.14.80-223-g8ea94372bf00) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.1… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.14.y/kernel/v4.14.80-22… Tree: stable-rc Branch: linux-4.14.y Git Describe: v4.14.80-223-g8ea94372bf00 Git Commit: 8ea94372bf0017762d8c4f9e2a53800304820e0e Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 54 unique boards, 21 SoC families, 15 builds out of 185 Boot Regressions Detected: arm: bcm2835_defconfig: bcm2837-rpi-3-b: lab-baylibre: failing since 1 day (last pass: v4.14.79-32-g24f453c41e18 - first fail: v4.14.80) exynos_defconfig: exynos5422-odroidxu3: lab-baylibre-seattle: new failure (last pass: v4.14.80-223-gaa871c61a152) multi_v7_defconfig: imx6q-sabrelite: lab-baylibre: failing since 1 day (last pass: v4.14.79 - first fail: v4.14.80) meson8b-odroidc1: lab-baylibre: failing since 1 day (last pass: v4.14.79 - first fail: v4.14.80) arm64: defconfig: bcm2837-rpi-3-b: lab-baylibre: failing since 1 day (last pass: v4.14.79 - first fail: v4.14.80) meson-gxbb-nanopi-k2: lab-baylibre: failing since 1 day (last pass: v4.14.79 - first fail: v4.14.80) meson-gxl-s905x-khadas-vim: lab-baylibre: failing since 1 day (last pass: v4.14.79 - first fail: v4.14.80) meson-gxl-s905x-libretech-cc: lab-baylibre: failing since 1 day (last pass: v4.14.79 - first fail: v4.14.80) qemu: lab-baylibre: failing since 1 day (last pass: v4.14.79 - first fail: v4.14.80) x86: x86_64_defconfig: qemu: lab-baylibre: failing since 1 day (last pass: v4.14.79-32-g24f453c41e18 - first fail: v4.14.80) Boot Failures Detected: arm: bcm2835_defconfig bcm2837-rpi-3-b: 1 failed lab multi_v7_defconfig imx6q-sabrelite: 1 failed lab arm64: defconfig meson-gxbb-nanopi-k2: 1 failed lab meson-gxl-s905x-libretech-cc: 1 failed lab Offline Platforms: arm: omap2plus_defconfig: am335x-boneblack: 1 offline lab sunxi_defconfig: sun5i-r8-chip: 1 offline lab tegra_defconfig: tegra124-jetson-tk1: 1 offline lab bcm2835_defconfig: bcm2835-rpi-b: 1 offline lab sama5_defconfig: at91-sama5d4_xplained: 1 offline lab multi_v7_defconfig: alpine-db: 1 offline lab am335x-boneblack: 1 offline lab at91-sama5d4_xplained: 1 offline lab socfpga_cyclone5_de0_sockit: 1 offline lab sun5i-r8-chip: 1 offline lab tegra124-jetson-tk1: 1 offline lab arm64: defconfig: apq8016-sbc: 1 offline lab juno-r2: 1 offline lab meson-gxl-s905d-p230: 1 offline lab meson-gxl-s905x-p212: 1 offline lab mt7622-rfb1: 1 offline lab Conflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) arm: vexpress_defconfig: qemu: lab-baylibre: FAIL lab-mhart: PASS multi_v7_defconfig: qemu: lab-baylibre: FAIL lab-mhart: PASS meson8b-odroidc1: lab-baylibre: FAIL lab-baylibre-seattle: PASS exynos_defconfig: exynos5422-odroidxu3: lab-baylibre: PASS lab-baylibre-seattle: FAIL arm64: defconfig: qemu: lab-baylibre: FAIL lab-mhart: PASS bcm2837-rpi-3-b: lab-baylibre: FAIL lab-mhart: PASS meson-gxl-s905x-khadas-vim: lab-baylibre: FAIL lab-baylibre-seattle: PASS x86: x86_64_defconfig: qemu: lab-baylibre: FAIL lab-mhart: PASS --- For more info write to <info(a)kernelci.org>

6 years, 9 months

1
0
0 0

stable-rc/linux-4.19.y boot: 98 boots: 9 failed, 65 passed with 16 offline, 8 conflicts (v4.19.1-362-g9ac3c2d4889c)

by kernelci.org bot

stable-rc/linux-4.19.y boot: 98 boots: 9 failed, 65 passed with 16 offline, 8 conflicts (v4.19.1-362-g9ac3c2d4889c) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.1… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.19.y/kernel/v4.19.1-362… Tree: stable-rc Branch: linux-4.19.y Git Describe: v4.19.1-362-g9ac3c2d4889c Git Commit: 9ac3c2d4889c84e1fa030dc61ca5aeb6951f8776 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 56 unique boards, 21 SoC families, 15 builds out of 187 Boot Regressions Detected: arm: bcm2835_defconfig: bcm2837-rpi-3-b: lab-baylibre: failing since 1 day (last pass: v4.19.1 - first fail: v4.19.1-362-gc881caaeb264) multi_v7_defconfig: imx6q-sabrelite: lab-baylibre: failing since 1 day (last pass: v4.19.1 - first fail: v4.19.1-362-gc881caaeb264) meson8b-odroidc1: lab-baylibre: failing since 1 day (last pass: v4.19.1 - first fail: v4.19.1-362-gc881caaeb264) sun8i-h2-plus-libretech-all-h3-cc: lab-baylibre: failing since 1 day (last pass: v4.19.1 - first fail: v4.19.1-362-gc881caaeb264) sun8i-h3-libretech-all-h3-cc: lab-baylibre: failing since 1 day (last pass: v4.19.1 - first fail: v4.19.1-362-gc881caaeb264) sunxi_defconfig: sun8i-h2-plus-libretech-all-h3-cc: lab-baylibre: failing since 1 day (last pass: v4.19.1 - first fail: v4.19.1-362-gc881caaeb264) sun8i-h3-libretech-all-h3-cc: lab-baylibre: failing since 1 day (last pass: v4.19.1 - first fail: v4.19.1-362-gc881caaeb264) arm64: defconfig: bcm2837-rpi-3-b: lab-baylibre: failing since 1 day (last pass: v4.19.1 - first fail: v4.19.1-362-gc881caaeb264) meson-gxl-s905x-khadas-vim: lab-baylibre: failing since 1 day (last pass: v4.19.1 - first fail: v4.19.1-362-gc881caaeb264) meson-gxl-s905x-libretech-cc: lab-baylibre: failing since 1 day (last pass: v4.19.1 - first fail: v4.19.1-362-gc881caaeb264) sun50i-h5-libretech-all-h3-cc: lab-baylibre: failing since 1 day (last pass: v4.19.1 - first fail: v4.19.1-362-gc881caaeb264) x86: x86_64_defconfig: qemu: lab-baylibre: failing since 1 day (last pass: v4.19.1 - first fail: v4.19.1-362-gc881caaeb264) Boot Failures Detected: arm: bcm2835_defconfig bcm2837-rpi-3-b: 1 failed lab sunxi_defconfig sun8i-h2-plus-libretech-all-h3-cc: 1 failed lab sun8i-h3-libretech-all-h3-cc: 1 failed lab multi_v7_defconfig imx6q-sabrelite: 1 failed lab sun8i-h2-plus-libretech-all-h3-cc: 1 failed lab sun8i-h3-libretech-all-h3-cc: 1 failed lab arm64: defconfig meson-gxbb-nanopi-k2: 1 failed lab meson-gxl-s905x-libretech-cc: 1 failed lab sun50i-h5-libretech-all-h3-cc: 1 failed lab Offline Platforms: arm: omap2plus_defconfig: am335x-boneblack: 1 offline lab sunxi_defconfig: sun5i-r8-chip: 1 offline lab tegra_defconfig: tegra124-jetson-tk1: 1 offline lab bcm2835_defconfig: bcm2835-rpi-b: 1 offline lab sama5_defconfig: at91-sama5d4_xplained: 1 offline lab multi_v7_defconfig: alpine-db: 1 offline lab am335x-boneblack: 1 offline lab at91-sama5d4_xplained: 1 offline lab socfpga_cyclone5_de0_sockit: 1 offline lab sun5i-r8-chip: 1 offline lab tegra124-jetson-tk1: 1 offline lab arm64: defconfig: apq8016-sbc: 1 offline lab juno-r2: 1 offline lab meson-gxl-s905d-p230: 1 offline lab meson-gxl-s905x-p212: 1 offline lab mt7622-rfb1: 1 offline lab Conflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) arm: multi_v7_defconfig: qemu: lab-baylibre: FAIL lab-mhart: PASS meson8b-odroidc1: lab-baylibre: FAIL lab-baylibre-seattle: PASS vexpress_defconfig: qemu: lab-baylibre: FAIL lab-mhart: PASS arm64: defconfig: bcm2837-rpi-3-b: lab-baylibre: FAIL lab-mhart: PASS lab-baylibre-seattle: PASS meson-gxl-s905x-khadas-vim: lab-baylibre: FAIL lab-baylibre-seattle: PASS qemu: lab-baylibre: FAIL lab-mhart: PASS meson-gxbb-p200: lab-baylibre: FAIL lab-baylibre-seattle: PASS x86: x86_64_defconfig: qemu: lab-baylibre: FAIL lab-mhart: PASS --- For more info write to <info(a)kernelci.org>

6 years, 9 months

1
0
0 0

stable-rc/linux-4.18.y boot: 100 boots: 9 failed, 68 passed with 16 offline, 7 conflicts (v4.18.18-351-ga77acf393de0)

by kernelci.org bot

stable-rc/linux-4.18.y boot: 100 boots: 9 failed, 68 passed with 16 offline, 7 conflicts (v4.18.18-351-ga77acf393de0) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.18.y/kernel/v4.1… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.18.y/kernel/v4.18.18-35… Tree: stable-rc Branch: linux-4.18.y Git Describe: v4.18.18-351-ga77acf393de0 Git Commit: a77acf393de04dda4d98962043a030467400b27f Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 57 unique boards, 21 SoC families, 15 builds out of 187 Boot Regressions Detected: arm: bcm2835_defconfig: bcm2837-rpi-3-b: lab-baylibre: failing since 1 day (last pass: v4.18.17-35-g46c86a0ac4a1 - first fail: v4.18.18) multi_v7_defconfig: imx6q-sabrelite: lab-baylibre: failing since 1 day (last pass: v4.18.17 - first fail: v4.18.18-351-g3c7d01cd1ddb) meson8b-odroidc1: lab-baylibre: failing since 1 day (last pass: v4.18.17 - first fail: v4.18.18-351-g3c7d01cd1ddb) sun8i-h2-plus-libretech-all-h3-cc: lab-baylibre: failing since 1 day (last pass: v4.18.17 - first fail: v4.18.18-351-g3c7d01cd1ddb) sun8i-h3-libretech-all-h3-cc: lab-baylibre: failing since 1 day (last pass: v4.18.17 - first fail: v4.18.18-351-g3c7d01cd1ddb) sunxi_defconfig: sun8i-h2-plus-libretech-all-h3-cc: lab-baylibre: failing since 1 day (last pass: v4.18.17-35-g46c86a0ac4a1 - first fail: v4.18.18) sun8i-h3-libretech-all-h3-cc: lab-baylibre: failing since 1 day (last pass: v4.18.17-35-g46c86a0ac4a1 - first fail: v4.18.18) arm64: defconfig: bcm2837-rpi-3-b: lab-baylibre: failing since 1 day (last pass: v4.18.17-35-g46c86a0ac4a1 - first fail: v4.18.18-351-g3c7d01cd1ddb) meson-gxbb-nanopi-k2: lab-baylibre: failing since 1 day (last pass: v4.18.17-35-g46c86a0ac4a1 - first fail: v4.18.18-351-g3c7d01cd1ddb) meson-gxl-s905x-khadas-vim: lab-baylibre: failing since 1 day (last pass: v4.18.17-35-g46c86a0ac4a1 - first fail: v4.18.18-351-g3c7d01cd1ddb) meson-gxl-s905x-libretech-cc: lab-baylibre: failing since 1 day (last pass: v4.18.17-35-g46c86a0ac4a1 - first fail: v4.18.18-351-g3c7d01cd1ddb) qemu: lab-baylibre: failing since 1 day (last pass: v4.18.17-35-g46c86a0ac4a1 - first fail: v4.18.18-351-g3c7d01cd1ddb) sun50i-h5-libretech-all-h3-cc: lab-baylibre: failing since 1 day (last pass: v4.18.17-35-g46c86a0ac4a1 - first fail: v4.18.18-351-g3c7d01cd1ddb) x86: x86_64_defconfig: qemu: lab-baylibre: failing since 1 day (last pass: v4.18.17-35-g46c86a0ac4a1 - first fail: v4.18.18) Boot Failures Detected: arm: bcm2835_defconfig bcm2837-rpi-3-b: 1 failed lab sunxi_defconfig sun8i-h2-plus-libretech-all-h3-cc: 1 failed lab sun8i-h3-libretech-all-h3-cc: 1 failed lab multi_v7_defconfig imx6q-sabrelite: 1 failed lab sun8i-h2-plus-libretech-all-h3-cc: 1 failed lab sun8i-h3-libretech-all-h3-cc: 1 failed lab arm64: defconfig meson-gxbb-nanopi-k2: 1 failed lab meson-gxl-s905x-libretech-cc: 1 failed lab sun50i-h5-libretech-all-h3-cc: 1 failed lab Offline Platforms: arm: omap2plus_defconfig: am335x-boneblack: 1 offline lab sunxi_defconfig: sun5i-r8-chip: 1 offline lab tegra_defconfig: tegra124-jetson-tk1: 1 offline lab bcm2835_defconfig: bcm2835-rpi-b: 1 offline lab sama5_defconfig: at91-sama5d4_xplained: 1 offline lab multi_v7_defconfig: alpine-db: 1 offline lab am335x-boneblack: 1 offline lab at91-sama5d4_xplained: 1 offline lab socfpga_cyclone5_de0_sockit: 1 offline lab sun5i-r8-chip: 1 offline lab tegra124-jetson-tk1: 1 offline lab arm64: defconfig: apq8016-sbc: 1 offline lab juno-r2: 1 offline lab meson-gxl-s905d-p230: 1 offline lab meson-gxl-s905x-p212: 1 offline lab mt7622-rfb1: 1 offline lab Conflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) arm: multi_v7_defconfig: meson8b-odroidc1: lab-baylibre: FAIL lab-baylibre-seattle: PASS qemu: lab-baylibre: FAIL lab-mhart: PASS vexpress_defconfig: qemu: lab-baylibre: FAIL lab-mhart: PASS arm64: defconfig: bcm2837-rpi-3-b: lab-baylibre: FAIL lab-mhart: PASS lab-baylibre-seattle: PASS qemu: lab-baylibre: FAIL lab-mhart: PASS meson-gxl-s905x-khadas-vim: lab-baylibre: FAIL lab-baylibre-seattle: PASS x86: x86_64_defconfig: qemu: lab-baylibre: FAIL lab-mhart: PASS --- For more info write to <info(a)kernelci.org>

6 years, 9 months

1
0
0 0

PASS: Test report for kernel 4.18.19-rc1.skt+ (linux-stable-rc)

by CKI

Hello, We ran automated tests on a recent commit from this kernel tree: Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Commit: a77acf393de0 Linux 4.18.19-rc1 The results of these automated tests are provided below. Overall result: PASSED Patch merge: OK Compile: OK Hardware test: OK Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. ,-. ,-. ( C ) ( I ) Continuous `-',-.`-' Kernel ( K ) Integration `-' ______________________________________________________________________________ Compile testing --------------- We compiled the kernel for 4 architectures: powerpc: make options: make INSTALL_MOD_STRIP=1 -j56 targz-pkg configuration: https://artifacts.cki-project.org/builds/ppc64le/a77acf393de04dda4d98962043… powerpc: make options: make INSTALL_MOD_STRIP=1 -j56 targz-pkg configuration: https://artifacts.cki-project.org/builds/ppc64/a77acf393de04dda4d98962043a0… arm64: make options: make INSTALL_MOD_STRIP=1 -j56 targz-pkg configuration: https://artifacts.cki-project.org/builds/aarch64/a77acf393de04dda4d98962043… x86_64: make options: make INSTALL_MOD_STRIP=1 -j56 targz-pkg configuration: https://artifacts.cki-project.org/builds/x86_64/a77acf393de04dda4d98962043a…

6 years, 9 months

1
0
0 0

stable-rc/linux-4.9.y boot: 81 boots: 2 failed, 61 passed with 14 offline, 4 conflicts (v4.9.136-142-g36c7703938e8)

by kernelci.org bot

stable-rc/linux-4.9.y boot: 81 boots: 2 failed, 61 passed with 14 offline, 4 conflicts (v4.9.136-142-g36c7703938e8) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.… Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.9.y/kernel/v4.9.136-142… Tree: stable-rc Branch: linux-4.9.y Git Describe: v4.9.136-142-g36c7703938e8 Git Commit: 36c7703938e83937f64cf8e08b857db562d1d2c9 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 43 unique boards, 20 SoC families, 16 builds out of 182 Boot Regressions Detected: arm: multi_v7_defconfig: imx6q-sabrelite: lab-baylibre: failing since 1 day (last pass: v4.9.135-156-gdb1dd7ad04c4 - first fail: v4.9.136) meson8b-odroidc1: lab-baylibre: failing since 1 day (last pass: v4.9.135-156-gdb1dd7ad04c4 - first fail: v4.9.136) x86: x86_64_defconfig: qemu: lab-baylibre: failing since 1 day (last pass: v4.9.135-172-gcc46a1dedc8b - first fail: v4.9.136) Boot Failures Detected: arm: multi_v7_defconfig imx6q-sabrelite: 1 failed lab meson8b-odroidc1: 1 failed lab Offline Platforms: arm: omap2plus_defconfig: am335x-boneblack: 1 offline lab sunxi_defconfig: sun5i-r8-chip: 1 offline lab tegra_defconfig: tegra124-jetson-tk1: 1 offline lab bcm2835_defconfig: bcm2835-rpi-b: 1 offline lab sama5_defconfig: at91-sama5d4_xplained: 1 offline lab multi_v7_defconfig: alpine-db: 1 offline lab am335x-boneblack: 1 offline lab at91-sama5d4_xplained: 1 offline lab socfpga_cyclone5_de0_sockit: 1 offline lab sun5i-r8-chip: 1 offline lab tegra124-jetson-tk1: 1 offline lab socfpga_defconfig: socfpga_cyclone5_de0_sockit: 1 offline lab arm64: defconfig: apq8016-sbc: 1 offline lab juno-r2: 1 offline lab Conflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) arm: multi_v7_defconfig: qemu: lab-baylibre: FAIL lab-mhart: PASS vexpress_defconfig: qemu: lab-baylibre: FAIL lab-mhart: PASS arm64: defconfig: qemu: lab-baylibre: FAIL lab-mhart: PASS x86: x86_64_defconfig: qemu: lab-baylibre: FAIL lab-mhart: PASS --- For more info write to <info(a)kernelci.org>

6 years, 9 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Linux-stable-mirror