Re: [PATCH v2 29/30] cxlflash: Fix to avoid state change collision

2015-09-21 Thread Matthew R. Ochs
> On Sep 21, 2015, at 7:44 AM, Tomas Henzl wrote: > On 16.9.2015 23:32, Matthew R. Ochs wrote: >> The adapter state machine is susceptible to missing and/or >> corrupting state updates at runtime. This can lead to a variety >> of unintended issues and is due to the lack of a serialization >> mecha

Re: [PATCH v2 29/30] cxlflash: Fix to avoid state change collision

2015-09-21 Thread Tomas Henzl
On 16.9.2015 23:32, Matthew R. Ochs wrote: > The adapter state machine is susceptible to missing and/or > corrupting state updates at runtime. This can lead to a variety > of unintended issues and is due to the lack of a serialization > mechanism to protect the adapter state. > > Use an adapter-wid

[PATCH v2 29/30] cxlflash: Fix to avoid state change collision

2015-09-16 Thread Matthew R. Ochs
The adapter state machine is susceptible to missing and/or corrupting state updates at runtime. This can lead to a variety of unintended issues and is due to the lack of a serialization mechanism to protect the adapter state. Use an adapter-wide mutex to serialize state changes. Signed-off-by: Ma

[PATCH v2 29/30] cxlflash: Fix to avoid state change collision

2015-09-16 Thread Matthew R. Ochs
The adapter state machine is susceptible to missing and/or corrupting state updates at runtime. This can lead to a variety of unintended issues and is due to the lack of a serialization mechanism to protect the adapter state. Use an adapter-wide mutex to serialize state changes. Signed-off-by: Ma