github-vet / github-vet/rangeloop-pointer-findings
a0x8o/kubernetes: staging/src/k8s.io/apiserver/pkg/server/openapi/openapi_aggregator.go; 3 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [a0x8o/kubernetes](https://www.github.com/a0x8o/kubernetes) at [staging/src/k8s.io/apiserver/pkg/server/openapi/openapi_aggregator.go](https://github.com/a0x8o/kubernetes/blob/06e98f7a27a6d2f408ed1ce068bc95f00d1c467d/staging/src/k8s.io/apiserver/pkg/server/openapi/openapi_aggregator.go#L88-L90)
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.
> function call at line 89 may store a reference to v
[Click here to see the code in its original context.](https://github.com/a0x8o/kubernetes/blob/06e98f7a27a6d2f408ed1ce068bc95f00d1c467d/staging/src/k8s.io/apiserver/pkg/server/openapi/openapi_aggregator.go#L88-L90)
Click here to show the 3 line(s) of Go which triggered the analyzer.
```go
for _, v := range schema.OneOf {
s.walkSchema(&v)
}
```
Click here to show extra information the analyzer produced.
```
The following graphviz dot graph describes paths through the callgraph that could lead to a function which writes a pointer argument:
digraph G {
"(walkSchema, 1)" -> {}
}
No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.
```
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: 06e98f7a27a6d2f408ed1ce068bc95f00d1c467d
Contributor guide
No contributing guide indexed for this repository
Research direction
Inspect staging/src/k8s.io/apiserver/pkg/server/openapi/openapi_aggregator.go around lines 88-90 and read the walkSchema call. Determine whether taking a pointer to the range variable v creates a real issue in this context, using the linked analyzer details and surrounding code. Done means leaving the requested Bug, Mitigated, or Desirable Behavior reaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100