libopenstorage/stork: drivers/volume/csi/csi.go; 3 LoC

Found a possible issue in [libopenstorage/stork](https://www.github.com/libopenstorage/stork) at [drivers/volume/csi/csi.go](https://github.com/libopenstorage/stork/blob/e8f89f1bdccc1c40b2da55520e148f697922bbb8/drivers/volume/csi/csi.go#L541-L543)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

> reference to vsContent is reassigned at line 542

[Click here to see the code in its original context.](https://github.com/libopenstorage/stork/blob/e8f89f1bdccc1c40b2da55520e148f697922bbb8/drivers/volume/csi/csi.go#L541-L543)

Click here to show the 3 line(s) of Go which triggered the analyzer.

```go
for _, vsContent := range vsContentList.Items {
vsContentMap[vsContent.Name] = &vsContent
}

```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: e8f89f1bdccc1c40b2da55520e148f697922bbb8

Read drivers/volume/csi/csi.go at lines 541-543 and inspect the surrounding range-loop context. Compare the referenced pointer use with the analyzer's range-loop finding guidance, then leave the requested reaction classifying it as a bug, mitigated, or desirable behavior.

Written by the indexing model from the issue text.