linux-kernel - Re: [PATCH] tpm_tis: fix tis

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <alpine.LNX.2.00.1203032340452.23367@pobox.suse.cz>
Date:	Sat, 3 Mar 2012 23:41:51 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Stefan Berger <stefanb@...ux.vnet.ibm.com>
Cc:	Rajiv Andrade <srajiv@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	tpmdd-devel@...ts.sourceforge.net
Subject: Re: [PATCH] tpm_tis: fix tis_lock with respect to RCU

On Wed, 29 Feb 2012, Stefan Berger wrote:

> > cleanup_tis() ->  tpm_remove_hardware() ->  syncrhonize_rcu() is being
> > called in an atomic context (tis_lock spinlock held), which is not
> > allowed. Convert tis_lock to mutex.
> > 
> > Signed-off-by: Jiri Kosina<jkosina@...e.cz>
> Tested-by: Stefan Berger <stefanb@...ux.vnet.ibm.com>

Thanks. Doesn't seem to have been picked up for -next yet. Which tree is 
this going through?

As a last resort, I can take it through trivial, but I guess for example 
Andrew's tree would be better.

-- 
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/