DESCRIPTION

tmf: Protect HTNode accesses with a reader/writer lock

Some funny things could happen in multi-thread scenarios, especially
if someone is querying the node while it is being written to disk.

Change-Id: Icbd5e1a5edf3118f9aa8e4827ba865b9b6f6f8ab
Signed-off-by: Braxton Mccarthy xxx@xxx.xxx


COMMENTS

author: Braxton Mccarthy
date: 2014-01-28 22:04:48.000000000

Uploaded patch set 2.

-------------------------------------
author: Brenden Conley
date: 2014-01-29 00:44:31.000000000

Patch Set 2:

Build Started https://hudson.eclipse.org/linuxtools/job/linuxtools-gerrit/5240/

-------------------------------------
author: Brenden Conley
date: 2014-01-29 01:31:34.000000000

Patch Set 2: Verified+1

Build Successful 

https://hudson.eclipse.org/linuxtools/job/linuxtools-gerrit/5240/ : SUCCESS

-------------------------------------
author: Ivy Mitchell
date: 2014-02-06 22:39:37.000000000

Patch Set 2: IP-Clean+1

Nothing objectable, any test cases recommended for this?

-------------------------------------
author: Braxton Mccarthy
date: 2014-02-06 22:58:27.000000000

Patch Set 2:

I think https://git.eclipse.org/r/#/c/20526/  could trigger this bug too. All the series of recent fixes for concurrency could be tested with either that test, or just opening a kernel trace in the UI.

-------------------------------------
author: Kaeden Tapia
date: 2014-02-11 21:17:24.000000000

Patch Set 2: Verified+1 Code-Review+2 IP-Clean+1

-------------------------------------
