[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191211174639.GH4516@linux.intel.com>
Date: Wed, 11 Dec 2019 19:47:01 +0200
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Tadeusz Struk <tadeusz.struk@...el.com>
Cc: peterz@...radead.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org, jgg@...pe.ca, mingo@...hat.com,
jeffrin@...agiritech.edu.in, linux-integrity@...r.kernel.org,
will@...nel.org, peterhuewe@....de
Subject: Re: [PATCH] tpm: fix WARNING: lock held when returning to user space
On Tue, Dec 10, 2019 at 01:17:51PM -0800, Tadeusz Struk wrote:
> When an application sends TPM commands in NONBLOCKING mode
> the driver holds chip->tpm_mutex returning from write(),
> which triggers WARNING: lock held when returning to user space!
> To silence this warning the driver needs to release the mutex
> and acquire it again in tpm_dev_async_work() before sending
> the command.
>
> Cc: stable@...r.kernel.org
> Fixes: 9e1b74a63f776 (tpm: add support for nonblocking operation)
> Signed-off-by: Tadeusz Struk <tadeusz.struk@...el.com>
Bundle the patch and test into same patch set (no need for
cover letter) in the case we need to iterate (as they must
be in sync anyway).
/Jarkko
Powered by blists - more mailing lists