-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
net: high cpu usage in extractExtendedRCode #66754
Comments
This code is processing DNS packets. It would help to know what DNS names are being looked up. That said, at least part of the problem is that methods like Still, it should only be an issue if the DNS server is returning a lot of additional headers. It's not clear why that would be happening. We started looking at the additional headers in https://go.dev/cl/514835. CC @mateusz834 |
Yep, this looks like a DNS response with a bunch of Additional resources, it would be helpful if you could provide us with the raw DNS message reply. |
Change https://go.dev/cl/578375 mentions this issue: |
This will avoid a potential endless loop for a corrupt DNS packet. For #66754 Change-Id: I46591b3f7695bcc88d2312833e45955f8c129d2b Reviewed-on: https://go-review.googlesource.com/c/go/+/578375 Reviewed-by: Damien Neil <dneil@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Commit-Queue: Ian Lance Taylor <iant@google.com> Auto-Submit: Ian Lance Taylor <iant@google.com> Reviewed-by: Ian Lance Taylor <iant@google.com>
@gopherbot please open backport issues, this is a PUBLIC track security issue. |
Backport issue(s) opened: Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases. |
Change https://go.dev/cl/581816 mentions this issue: |
This comment was marked as resolved.
This comment was marked as resolved.
This will avoid a potential endless loop for a corrupt DNS packet. For #66754 Fixes #67040 Change-Id: I46591b3f7695bcc88d2312833e45955f8c129d2b Reviewed-on: https://go-review.googlesource.com/c/go/+/578375 Reviewed-by: Damien Neil <dneil@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Commit-Queue: Ian Lance Taylor <iant@google.com> Auto-Submit: Ian Lance Taylor <iant@google.com> Reviewed-by: Ian Lance Taylor <iant@google.com> (cherry picked from commit ddfab21) Reviewed-on: https://go-review.googlesource.com/c/go/+/581816 Reviewed-by: David Chase <drchase@google.com>
CL submitted. Closing. Thanks. |
see golang/go#66754 released with go1.22.3. also check error for new SkipAdditional call related to extended dns errors.
Go version
go 1.22.2 linux/amd64
Output of
go env
in your module/workspace:What did you do?
concurrent calls to net.LookupAddr
What did you see happen?
pprof seems that goLookupIp may causes high cpu usage
profile.zip
What did you expect to see?
Occasionally, I don’t know what domain name it was when it happened.
The text was updated successfully, but these errors were encountered: