github-vet / github-vet/rangeloop-pointer-findings
yunify/hostnic-cni: pkg/netlinkwrapper/netlinkwrapper.go; 3 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [yunify/hostnic-cni](https://www.github.com/yunify/hostnic-cni) at [pkg/netlinkwrapper/netlinkwrapper.go](https://github.com/yunify/hostnic-cni/blob/edfa643b8b52f01cb985dacb80d61f8ea109c8bf/pkg/netlinkwrapper/netlinkwrapper.go#L108-L110)
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 109 passes reference to rule to third-party code
[Click here to see the code in its original context.](https://github.com/yunify/hostnic-cni/blob/edfa643b8b52f01cb985dacb80d61f8ea109c8bf/pkg/netlinkwrapper/netlinkwrapper.go#L108-L110)
Click here to show the 3 line(s) of Go which triggered the analyzer.
```go
for _, rule := range rules {
n.RuleDel(&rule)
}
```
Click here to show extra information the analyzer produced.
```
No path was found through the callgraph that could lead to a function which writes a pointer argument.
The following graphviz dot graph describes paths through the callgraph that could lead to a function which passes a pointer to third-party code:
digraph G {
"(RuleDel, 1)" -> {}
}
```
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: edfa643b8b52f01cb985dacb80d61f8ea109c8bf
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at pkg/netlinkwrapper/netlinkwrapper.go lines 108-110 and inspect the surrounding range over rules and the RuleDel call. Read the analyzer guidance linked in the issue, then determine whether this instance is a Bug, Mitigated, or Desirable Behavior and record that classification as the completed work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100