Flush returning "Receive: netlink receive: recvmsg: no buffer space available"
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go, linux
- Domain
- networking
Research direction
Start at Flush() and trace the netlink receive path associated with the reported recvmsg error. Reproduce the failure by combining messages whose payload crosses the netlink buffer size, then determine the expected application-facing behavior or API and document it with a regression test.
Written by the indexing model from the issue text.
Description
I observed that when we combine multiple messages and call Flush, the Flush may fail (with error "Receive: netlink receive: recvmsg: no buffer space available") if the message payload crosses netlink buffer size.
Currently Flush() doesn't handle it? is application supposed to handle it? is there any API exposed from which application can know if the netlink message size is exceeded?
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 187
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from google/nftables
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
-
Multiple Netlink Decode Paths Can Panic on Malformed or Undersized InputPossibly taken @vulragrag-star claimed this 33 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 68/100
-
New Tag release.Open
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Merge set elementsOpen
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Similar issues
-
automation models
Difficulty 1/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 91/100
Maintainers usually reply within 1 day
-
confirmed enhancement go
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
DennisVlaanderen/aerendil#154 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
crossplane-contrib/provider-mongodbatlas#236 ·
Maintainers usually reply within 1 day
-
Generated README and SKILL omit HTTP-transport security settings and what local data the CLI keepsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
mvanhorn/cli-printing-press#5181 ·
Maintainers usually reply within 1 day