Re: [PATCH 4.19 00/24] 4.19.176-rc1 review
On 2/11/21 8:02 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.19.176 release. There are 24 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 Sat, 13 Feb 2021 15:01:39 +. 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/v4.x/stable-review/patch-4.19.176-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-4.19.y and the diffstat can be found below. thanks, greg k-h Compiled and booted on my test system. No dmesg regressions. Tested-by: Shuah Khan thanks, -- Shuah
Re: [PATCH 4.19 00/24] 4.19.176-rc1 review
On Fri, Feb 12, 2021 at 03:59:41PM +0530, Naresh Kamboju wrote: > On Fri, 12 Feb 2021 at 13:12, Greg Kroah-Hartman > wrote: > > > > On Fri, Feb 12, 2021 at 10:16:11AM +0530, Naresh Kamboju wrote: > > > On Thu, 11 Feb 2021 at 20:36, Greg Kroah-Hartman > > > wrote: > > > > > > > > This is the start of the stable review cycle for the 4.19.176 release. > > > > There are 24 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 Sat, 13 Feb 2021 15:01:39 +. > > > > 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/v4.x/stable-review/patch-4.19.176-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-4.19.y > > > > and the diffstat can be found below. > > > > > > > > thanks, > > > > > > > > greg k-h > > > > > > The following lockdep noticed on the arm beaglebone x15 device. > > > I have not bisected this problem yet. > > > Suspecting this patch, > > > > > > > David Collins > > > > regulator: core: avoid regulator_resolve_supply() race condition > > > > Sasha queued up a fix for this, let me push out a -rc2 with that in > > there to see if this resolves the issue. > > The reported issue is fixed on 4.19.176-rc2. Wonderful, thanks for letting me know. greg k-h
Re: [PATCH 4.19 00/24] 4.19.176-rc1 review
On Fri, 12 Feb 2021 at 13:12, Greg Kroah-Hartman wrote: > > On Fri, Feb 12, 2021 at 10:16:11AM +0530, Naresh Kamboju wrote: > > On Thu, 11 Feb 2021 at 20:36, Greg Kroah-Hartman > > wrote: > > > > > > This is the start of the stable review cycle for the 4.19.176 release. > > > There are 24 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 Sat, 13 Feb 2021 15:01:39 +. > > > 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/v4.x/stable-review/patch-4.19.176-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-4.19.y > > > and the diffstat can be found below. > > > > > > thanks, > > > > > > greg k-h > > > > The following lockdep noticed on the arm beaglebone x15 device. > > I have not bisected this problem yet. > > Suspecting this patch, > > > > > David Collins > > > regulator: core: avoid regulator_resolve_supply() race condition > > Sasha queued up a fix for this, let me push out a -rc2 with that in > there to see if this resolves the issue. The reported issue is fixed on 4.19.176-rc2. - Naresh
Re: [PATCH 4.19 00/24] 4.19.176-rc1 review
On Fri, Feb 12, 2021 at 10:16:11AM +0530, Naresh Kamboju wrote: > On Thu, 11 Feb 2021 at 20:36, Greg Kroah-Hartman > wrote: > > > > This is the start of the stable review cycle for the 4.19.176 release. > > There are 24 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 Sat, 13 Feb 2021 15:01:39 +. > > 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/v4.x/stable-review/patch-4.19.176-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-4.19.y > > and the diffstat can be found below. > > > > thanks, > > > > greg k-h > > The following lockdep noticed on the arm beaglebone x15 device. > I have not bisected this problem yet. > Suspecting this patch, > > > David Collins > > regulator: core: avoid regulator_resolve_supply() race condition Sasha queued up a fix for this, let me push out a -rc2 with that in there to see if this resolves the issue. thanks greg k-h
Re: [PATCH 4.19 00/24] 4.19.176-rc1 review
On Thu, 11 Feb 2021 at 20:36, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.176 release.
> There are 24 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 Sat, 13 Feb 2021 15:01:39 +.
> 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/v4.x/stable-review/patch-4.19.176-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-4.19.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
The following lockdep noticed on the arm beaglebone x15 device.
I have not bisected this problem yet.
Suspecting this patch,
> David Collins
> regulator: core: avoid regulator_resolve_supply() race condition
[2.470568] WARNING: possible recursive locking detected
[2.470580] 4.19.176-rc1 #1 Not tainted
[2.470590]
[2.470600] swapper/0/1 is trying to acquire lock:
[2.470611] (ptrval) (>mutex){+.+.}, at: regulator_enable+0x44/0x20c
[2.470639]
[2.470639] but task is already holding lock:
[2.470650] (ptrval) (>mutex){+.+.}, at:
regulator_lock_nested+0x28/0x88
[2.470676]
[2.470676] other info that might help us debug this:
[2.470687] Possible unsafe locking scenario:
[2.470687]
[2.470698]CPU0
[2.470707]
[2.470716] lock(>mutex);
[2.470728] lock(>mutex);
[2.470740]
[2.470740] *** DEADLOCK ***
[2.470740]
[2.470752] May be due to missing lock nesting notation
[2.470752]
[2.470765] 2 locks held by swapper/0/1:
[2.470774] #0: (ptrval) (>mutex){}, at: __driver_attach+0x78/0x168
[2.470797] #1: (ptrval) (>mutex){+.+.}, at:
regulator_lock_nested+0x28/0x88
[2.470820]
[2.470820] stack backtrace:
[2.470836] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.19.176-rc1 #1
[2.470846] Hardware name: Generic DRA74X (Flattened Device Tree)
[2.470871] [] (unwind_backtrace) from []
(show_stack+0x20/0x24)
[2.470891] [] (show_stack) from []
(dump_stack+0xe8/0x114)
[2.470910] [] (dump_stack) from []
(__lock_acquire+0x7cc/0x1acc)
[2.470925] [] (__lock_acquire) from []
(lock_acquire+0xdc/0x238)
[2.470941] [] (lock_acquire) from []
(__mutex_lock+0xa0/0xaf4)
[2.470958] [] (__mutex_lock) from []
(mutex_lock_nested+0x2c/0x34)
[2.470974] [] (mutex_lock_nested) from []
(regulator_enable+0x44/0x20c)
[2.470990] [] (regulator_enable) from []
(regulator_resolve_supply+0x184/0x2c8)
[2.471006] [] (regulator_resolve_supply) from
[] (regulator_register_resolve_supply+0x24/0x8c)
[2.471022] [] (regulator_register_resolve_supply) from
[] (class_for_each_device+0x70/0xe8)
[2.471037] [] (class_for_each_device) from []
(regulator_register+0xa18/0xc58)
[2.471053] [] (regulator_register) from []
(devm_regulator_register+0x54/0x84)
[2.471069] [] (devm_regulator_register) from
[] (pbias_regulator_probe+0x1f4/0x2d0)
[2.471084] [] (pbias_regulator_probe) from []
(platform_drv_probe+0x58/0xa8)
[2.471101] [] (platform_drv_probe) from []
(really_probe+0x310/0x418)
[2.471119] [] (really_probe) from []
(driver_probe_device+0x88/0x1dc)
[2.471135] [] (driver_probe_device) from []
(__driver_attach+0x14c/0x168)
[2.471150] [] (__driver_attach) from []
(bus_for_each_dev+0x84/0xc4)
[2.471167] [] (bus_for_each_dev) from []
(driver_attach+0x2c/0x30)
[2.471184] [] (driver_attach) from []
(bus_add_driver+0x1d0/0x274)
[2.471199] [] (bus_add_driver) from []
(driver_register+0x84/0x118)
[2.471213] [] (driver_register) from []
(__platform_driver_register+0x50/0x58)
[2.471231] [] (__platform_driver_register) from
[] (pbias_regulator_driver_init+0x24/0x28)
[2.471249] [] (pbias_regulator_driver_init) from
[] (do_one_initcall+0xa0/0x394)
[2.471268] [] (do_one_initcall) from []
(kernel_init_freeable+0x3ec/0x484)
[2.471283] [] (kernel_init_freeable) from []
(kernel_init+0x18/0x128)
[2.471299] [] (kernel_init) from []
(ret_from_fork+0x14/0x28)
[2.471310] Exception stack(0xee19bfb0 to 0xee19bff8)
[2.471323] bfa0:
[2.471336] bfc0:
[2.471348] bfe0: 0013
[2.471385] vtt_fixed: supplied by smps3
test log link,
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-4.19.y/build/v4.19.175-25-g30e16c3fd5ac/testrun/3938030/suite/linux-log-parser/test/check-kernel-warning-2263196/log
metadata:
git branch: linux-4.19.y
git repo:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git commit:
