Re: [PATCHv2] libfc: Update rport reference counting

2016-06-14 Thread Martin K. Petersen
> "Hannes" == Hannes Reinecke writes: Hannes> Originally libfc would just be initializing the refcount to '1', Hannes> and using the disc_mutex to synchronize if and when the final Hannes> put should be happening. This has a race condition as the mutex Hannes> might be

Re: [PATCHv2] libfc: Update rport reference counting

2016-06-14 Thread Johannes Thumshirn
On Tue, May 24, 2016 at 08:11:58AM +0200, Hannes Reinecke wrote: > Originally libfc would just be initializing the refcount to '1', > and using the disc_mutex to synchronize if and when the final put > should be happening. > This has a race condition as the mutex might be delayed, causing > other

Re: [PATCHv2] libfc: Update rport reference counting

2016-05-24 Thread Vasu Dev
On Tue, 2016-05-24 at 08:11 +0200, Hannes Reinecke wrote: > Originally libfc would just be initializing the refcount to '1', > and using the disc_mutex to synchronize if and when the final put > should be happening. > This has a race condition as the mutex might be delayed, causing > other threads

[PATCHv2] libfc: Update rport reference counting

2016-05-24 Thread Hannes Reinecke
Originally libfc would just be initializing the refcount to '1', and using the disc_mutex to synchronize if and when the final put should be happening. This has a race condition as the mutex might be delayed, causing other threads to access an invalid structure. This patch updates the rport