Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5A6B9C61DA4 for ; Tue, 14 Feb 2023 15:09:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232553AbjBNPJn (ORCPT ); Tue, 14 Feb 2023 10:09:43 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60910 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229502AbjBNPJl (ORCPT ); Tue, 14 Feb 2023 10:09:41 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 667351A4A4; Tue, 14 Feb 2023 07:09:40 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id EB2AC61710; Tue, 14 Feb 2023 15:09:39 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 48F81C433EF; Tue, 14 Feb 2023 15:09:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1676387379; bh=+AsNUxy45TD+Ac08lmO9s9mHelklBxorVBuMpp5lJsg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ZUl6jXAExkzVLePnTlMmCOGQbEKkUo7HiiH8qzn9oN1FDp2Lw7wzdvirMjDzxfjq3 R+ljp3apu8Xnh6lDCDI1O95Da0rcGZF1EZxi3l046vRiYoIl6ECwnXEL8PiyMNZTps 7eEvVQj55IyhSC/sipx/RBCIqxpxApFjQJ7afFFlNR57jlbZ66WAmBmvlEuKjWD4Yd 4d8/m05O5H5+g7DBJfrf7rl+NnI8rcvipg4Z4eHkdHexGSL6AB1wn3SmVjSf3zlDQj BDkOuOsspNwhbxbL/KmgDk1aMRsD0zFC416oEDk/fdUXLhR0btflvKvfP73M2Kowsr 9KbkPp8g4HV7Q== Date: Tue, 14 Feb 2023 10:09:38 -0500 From: Sasha Levin To: "Russell King (Oracle)" Cc: Greg Kroah-Hartman , Florian Fainelli , stable@vger.kernel.org, Srinivas Kandagatla , patches@lists.linux.dev, linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org, lkft-triage@lists.linaro.org, pavel@denx.de, jonathanh@nvidia.com, sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de Subject: Re: [PATCH 5.10 000/139] 5.10.168-rc1 review Message-ID: References: <20230213144745.696901179@linuxfoundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 14, 2023 at 02:53:13PM +0000, Russell King (Oracle) wrote: >On Tue, Feb 14, 2023 at 07:20:46AM +0100, Greg Kroah-Hartman wrote: >> On Mon, Feb 13, 2023 at 11:50:24AM -0800, Florian Fainelli wrote: >> > On 2/13/23 06:49, Greg Kroah-Hartman wrote: >> > > This is the start of the stable review cycle for the 5.10.168 release. >> > > There are 139 patches in this series, all will be posted as a response >> > > to this one. If anyone has any issues with these being applied, please >> > > let me know. >> > > >> > > Responses should be made by Wed, 15 Feb 2023 14:46:51 +0000. >> > > Anything received after that time might be too late. >> > > >> > > The whole patch series can be found in one patch at: >> > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.168-rc1.gz >> > > or in the git tree and branch at: >> > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y >> > > and the diffstat can be found below. >> > > >> > > thanks, >> > > >> > > greg k-h >> > >> > There is a regression coming from: >> > >> > nvmem: core: fix registration vs use race >> > >> > which causes the following to happen for MTD devices: >> > >> > [ 6.031640] kobject_add_internal failed for mtd0 with -EEXIST, don't try >> > to register things with the same name in the same directory. >> > [ 7.846965] spi-nor: probe of spi0.0 failed with error -17 >> > >> > attached is a full log with the call trace. This does not happen with >> > v6.2-rc8 where the MTD partitions are successfully registered. >> >> Can you use `git bisect` to find the offending commit? > >The reason for this is because, due to how my patch series was >backported, you have ended up with nvmem_register() initialising >its embedded device, and then calling device_add() on it _twice_. > >Basically, the backport of: > > "nvmem: core: fix registration vs use race" > >is broken, because the original patch _moved_ the device_add() and >that has not been carried forward to whatever got applied to stable >trees. > >It looks like the 5.15-stable version of this patch was correct. > >Maybe whoever tried to fixup the failure needs to try again? I've dropped the backport series from both 5.15 and 5.10. -- Thanks, Sasha