-
Notifications
You must be signed in to change notification settings - Fork 3.7k
SIGSEGV: invalid memory address or nil pointer dereference in DeviceNames #34019
Copy link
Copy link
Closed
Copy link
Labels
area/agentCilium agent related.Cilium agent related.kind/bugThis is a bug in the Cilium logic.This is a bug in the Cilium logic.kind/community-reportThis was reported by a user in the Cilium community, eg via Slack.This was reported by a user in the Cilium community, eg via Slack.needs/triageThis issue requires triaging to establish severity and next steps.This issue requires triaging to establish severity and next steps.priority/highThis is considered vital to an upcoming release.This is considered vital to an upcoming release.
Description
Is there an existing issue for this?
- I have searched the existing issues
Version
higher than v1.16.0 and lower than v1.17.0
What happened?
Since upgrading to Cilium 1.16.0, I sporadically observe Cilium Agent container crash/restarts caused by below nil pointer error:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x90 pc=0x2642570]
goroutine 984 [running]:
github.com/cilium/cilium/pkg/datapath/types.(*LocalNodeConfiguration).DeviceNames(...)
/go/src/github.com/cilium/cilium/pkg/datapath/types/node.go:165
github.com/cilium/cilium/pkg/datapath/linux/config.(*HeaderfileWriter).WriteEndpointConfig(0x4002798000, {0x3dce300, 0x4000da29e0?}, 0x0, {0x3e531f0, 0x4000468c08})
/go/src/github.com/cilium/cilium/pkg/datapath/linux/config/config.go:1045 +0xf0
github.com/cilium/cilium/pkg/datapath/loader.(*loader).WriteEndpointConfig(0x4000468c08?, {0x3dce300?, 0x4000da29e0?}, {0x3e531f0?, 0x4000468c08?})
/go/src/github.com/cilium/cilium/pkg/datapath/loader/loader.go:698 +0x50
github.com/cilium/cilium/pkg/endpoint.(*Endpoint).writeHeaderfile(0x4000468c08, {0x40029fbac0, 0x1a})
/go/src/github.com/cilium/cilium/pkg/endpoint/bpf.go:189 +0x540
github.com/cilium/cilium/pkg/endpoint.(*Endpoint).syncEndpointHeaderFile(0x4000468c08, {0x4001249720, 0x1, 0x1})
/go/src/github.com/cilium/cilium/pkg/endpoint/endpoint.go:2450 +0x294
github.com/cilium/cilium/pkg/trigger.(*Trigger).waiter(0x4002532960)
/go/src/github.com/cilium/cilium/pkg/trigger/trigger.go:201 +0x464
created by github.com/cilium/cilium/pkg/trigger.NewTrigger in goroutine 1
/go/src/github.com/cilium/cilium/pkg/trigger/trigger.go:122 +0x1b4
How can we reproduce the issue?
N/A
Cilium Version
1.16.0
Kernel Version
6.1.94
Bottlerocket OS 1.20.4 (aws-k8s-1.29)
containerd://1.6.31
Kubernetes Version
v1.29.4-eks-036c24b
Regression
No response
Sysdump
No response
Relevant log output
time="2024-07-25T18:20:29Z" level=info msg="Subscribed to CiliumNode custom resource" name=ip-10-176-21-6.eu-central-1.compute.internal subsys=ipam
time="2024-07-25T18:20:29Z" level=info msg="Creating or updating CiliumNode resource" node=ip-10-176-21-6.eu-central-1.compute.internal subsys=nodediscovery
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x90 pc=0x2642570]
goroutine 984 [running]:
github.com/cilium/cilium/pkg/datapath/types.(*LocalNodeConfiguration).DeviceNames(...)
/go/src/github.com/cilium/cilium/pkg/datapath/types/node.go:165
github.com/cilium/cilium/pkg/datapath/linux/config.(*HeaderfileWriter).WriteEndpointConfig(0x4002798000, {0x3dce300, 0x4000da29e0?}, 0x0, {0x3e531f0, 0x4000468c08})
/go/src/github.com/cilium/cilium/pkg/datapath/linux/config/config.go:1045 +0xf0
github.com/cilium/cilium/pkg/datapath/loader.(*loader).WriteEndpointConfig(0x4000468c08?, {0x3dce300?, 0x4000da29e0?}, {0x3e531f0?, 0x4000468c08?})
/go/src/github.com/cilium/cilium/pkg/datapath/loader/loader.go:698 +0x50
github.com/cilium/cilium/pkg/endpoint.(*Endpoint).writeHeaderfile(0x4000468c08, {0x40029fbac0, 0x1a})
/go/src/github.com/cilium/cilium/pkg/endpoint/bpf.go:189 +0x540
github.com/cilium/cilium/pkg/endpoint.(*Endpoint).syncEndpointHeaderFile(0x4000468c08, {0x4001249720, 0x1, 0x1})
/go/src/github.com/cilium/cilium/pkg/endpoint/endpoint.go:2450 +0x294
github.com/cilium/cilium/pkg/trigger.(*Trigger).waiter(0x4002532960)
/go/src/github.com/cilium/cilium/pkg/trigger/trigger.go:201 +0x464
created by github.com/cilium/cilium/pkg/trigger.NewTrigger in goroutine 1
/go/src/github.com/cilium/cilium/pkg/trigger/trigger.go:122 +0x1b4Anything else?
No response
Cilium Users Document
- Are you a user of Cilium? Please add yourself to the Users doc
Code of Conduct
- I agree to follow this project's Code of Conduct
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/agentCilium agent related.Cilium agent related.kind/bugThis is a bug in the Cilium logic.This is a bug in the Cilium logic.kind/community-reportThis was reported by a user in the Cilium community, eg via Slack.This was reported by a user in the Cilium community, eg via Slack.needs/triageThis issue requires triaging to establish severity and next steps.This issue requires triaging to establish severity and next steps.priority/highThis is considered vital to an upcoming release.This is considered vital to an upcoming release.