gluster/glusterd2: glusterd2/commands/volumes/bricks-status.go; 5 LoC

Found a possible issue in [gluster/glusterd2](https://www.github.com/gluster/glusterd2) at [glusterd2/commands/volumes/bricks-status.go](https://github.com/gluster/glusterd2/blob/54ce5f6f7a714b321b6fb74a34207f66277d64b6/glusterd2/commands/volumes/bricks-status.go#L96-L100)

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 b was used in a composite literal at line 98

[Click here to see the code in its original context.](https://github.com/gluster/glusterd2/blob/54ce5f6f7a714b321b6fb74a34207f66277d64b6/glusterd2/commands/volumes/bricks-status.go#L96-L100)

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

```go
for _, b := range vol.GetBricks() {
bmap[b.ID.String()] = api.BrickStatus{
Info: brick.CreateBrickInfo(&b),
}
}

```

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: 54ce5f6f7a714b321b6fb74a34207f66277d64b6

Read glusterd2/commands/volumes/bricks-status.go around lines 96-100 and review how the range variable b is passed into brick.CreateBrickInfo. Verify whether the pointer can produce incorrect brick data, then classify the finding as a bug, mitigated, or desirable behavior and leave the requested reaction.

Written by the indexing model from the issue text.