On Thu, Dec 12, 2019 at 03:13:37AM +0530, Jeffrin Jose wrote: > On Wed, Dec 11, 2019 at 04:04:49PM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 5.3.16 release. > > There are 105 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 Fri, 13 Dec 2019 14:56:06 +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.3.16-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.3.y > > and the diffstat can be found below. > > > > the following is from "dmesg -l warn" > > -------------------x------------x------------------------ > ================================================ > WARNING: lock held when returning to user space! > 5.3.16-rc1+ #1 Tainted: G E > ------------------------------------------------ > tpm2-abrmd/679 is leaving the kernel with locks still held! > 2 locks held by tpm2-abrmd/679: > #0: 00000000d3bc394f (&chip->ops_sem){.+.+}, at: tpm_try_get_ops+0x2b/0xb0 [tpm] > #1: 000000004a4d7099 (&chip->tpm_mutex){+.+.}, at: tpm_try_get_ops+0x4b/0xb0 [tpm] > > ------------x----------------------x--------------------- > > the fix for the above to a typical kernel is here ... > > https://patchwork.kernel.org/patch/11283317/ I need to wait for that to get into Linus's tree before we can do anything about it for a stable kernel release. thanks, greg k-h
