From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Will Deacon <will@kernel.org>
Cc: Jeffrin Jose <jeffrin@rajagiritech.edu.in>,
peterz@infradead.org, mingo@redhat.com,
linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
peterhuewe@gmx.de, jgg@ziepe.ca
Subject: Re: [PROBLEM]: WARNING: lock held when returning to user space! (5.4.1 #16 Tainted: G )
Date: Mon, 9 Dec 2019 22:25:52 +0200 [thread overview]
Message-ID: <20191209202552.GK19243@linux.intel.com> (raw)
In-Reply-To: <20191209103432.GC3306@willie-the-truck>
On Mon, Dec 09, 2019 at 10:34:32AM +0000, Will Deacon wrote:
> Hi,
>
> [expanding cc list]
>
> On Sat, Dec 07, 2019 at 11:04:20PM +0530, Jeffrin Jose wrote:
> > i got the following output related from typical dmesg output from 5.4.1 kernel
>
> Was this during boot or during some other operation?
>
> > ================================================
> > WARNING: lock held when returning to user space!
> > 5.4.1 #16 Tainted: G E
> > ------------------------------------------------
> > tpm2-abrmd/691 is leaving the kernel with locks still held!
> > 2 locks held by tpm2-abrmd/691:
> > #0: ffff8881ee784ba8 (&chip->ops_sem){.+.+}, at: tpm_try_get_ops+0x2b/0xc0 [tpm]
> > #1: ffff8881ee784d88 (&chip->tpm_mutex){+.+.}, at: tpm_try_get_ops+0x57/0xc0 [tpm]
>
> Can you reproduce this failure on v5.5-rc1?
Does this appear after variable amount of time or detemitically always
at certain point of time (e.g. when the daemon starts or perhaps always
when doing a certain operations with TSS)?
Do we have possibility to get the user code path that gets executed when
this happens?
/Jarkko
next prev parent reply other threads:[~2019-12-09 20:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-07 17:34 [PROBLEM]: WARNING: lock held when returning to user space! (5.4.1 #16 Tainted: G ) Jeffrin Jose
2019-12-09 10:34 ` Will Deacon
2019-12-09 20:25 ` Jarkko Sakkinen [this message]
2019-12-09 21:34 ` Tadeusz Struk
2019-12-10 19:04 ` [PATCH] tpm: selftest: add test covering async mode Tadeusz Struk
2019-12-11 17:42 ` Jarkko Sakkinen
2019-12-10 21:17 ` [PATCH] tpm: fix WARNING: lock held when returning to user space Tadeusz Struk
2019-12-11 17:47 ` Jarkko Sakkinen
2019-12-11 17:52 ` Jarkko Sakkinen
2019-12-11 18:00 ` Jarkko Sakkinen
2019-12-11 15:17 ` [PROBLEM]: WARNING: lock held when returning to user space! (5.4.1 #16 Tainted: G ) Jeffrin Jose
2019-12-11 18:36 ` Tadeusz Struk
2019-12-12 8:12 ` Jeffrin Jose
2019-12-11 17:45 ` Jarkko Sakkinen
2019-12-11 18:18 ` Jeffrin Jose
2019-12-11 18:22 ` Jeffrin Jose
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191209202552.GK19243@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jeffrin@rajagiritech.edu.in \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterhuewe@gmx.de \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.