linux-kernel - Re: [PATCH 3/4] TPM: rcu locking

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080923202701.GF6637@linux.vnet.ibm.com>
Date:	Tue, 23 Sep 2008 13:27:01 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Rajiv Andrade <srajiv@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	serue@...ux.vnet.ibm.com, zohar@...ux.vnet.ibm.com,
	safford@...son.ibm.com, debora@...ux.vnet.ibm.com
Subject: Re: [PATCH 3/4] TPM: rcu locking

On Tue, Sep 23, 2008 at 05:18:17PM -0300, Rajiv Andrade wrote:
> Paul,
> 
> On Tue, 2008-09-23 at 11:19 -0700, Paul E. McKenney wrote:
> > 
> > But here we are deleting from what appears to be some other list.
> > And I don't see any insertiong into either list.
> > 
> > What am I missing here?
> > 
> >                                                         Thanx, Paul
> 
> Sorry, forgot to change list_add() to list_add_rcu() in the code section
> below:
> 
> > > +     /* Make chip available */
> > > +     spin_lock(&driver_lock);
> > > +     list_add(&chip->list, &tpm_chip_list);
> > > +     spin_unlock(&driver_lock);
> 
> I'll resubmit.

Cool!

So tpm_chip_list and the not-obviously-identical list manipulated
in tpm_remove_hardware() really are the same list?

							Thanx, Paul
--
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/