Skip to content
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

winlogbeat/sys/wineventlog: don't use claimed buffer use value #35437

Merged
merged 1 commit into from
May 12, 2023

Conversation

efd6
Copy link
Contributor

@efd6 efd6 commented May 12, 2023

What does this PR do?

EvtFormatMessage appears to sometimes claim that more buffer was used during a rendering call than was or exists, so do not use this value except in the query to get the needed buffer size.

It is a subset of the change in #34005. The remainder of the removal of the passed buffer is left for later work.

Why is it important?

Winlogbeat will sometimes panic due to a bounds error.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

@efd6 efd6 added bug Winlogbeat 8.9-candidate backport-v8.8.0 Automated backport with mergify labels May 12, 2023
@efd6 efd6 self-assigned this May 12, 2023
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label May 12, 2023
@botelastic
Copy link

botelastic bot commented May 12, 2023

This pull request doesn't have a Team:<team> label.

EvtFormatMessage appears to sometimes claim that more buffer was used
during a rendering call than was or exists, so do not use this value
except in the query to get the needed buffer size.
@elasticmachine
Copy link
Collaborator

elasticmachine commented May 12, 2023

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-05-12T05:44:47.870+0000

  • Duration: 70 min 24 sec

Test stats 🧪

Test Results
Failed 0
Passed 26362
Skipped 1975
Total 28337

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@efd6 efd6 marked this pull request as ready for review May 12, 2023 06:25
@efd6 efd6 requested a review from a team as a code owner May 12, 2023 06:25
Copy link
Member

@andrewkroh andrewkroh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@efd6 efd6 merged commit fd7b89c into elastic:main May 12, 2023
mergify bot pushed a commit that referenced this pull request May 12, 2023
EvtFormatMessage appears to sometimes claim that more buffer was used
during a rendering call than was or exists, so do not use this value
except in the query to get the needed buffer size.

(cherry picked from commit fd7b89c)
efd6 added a commit that referenced this pull request May 14, 2023
… (#35442)

EvtFormatMessage appears to sometimes claim that more buffer was used
during a rendering call than was or exists, so do not use this value
except in the query to get the needed buffer size.

(cherry picked from commit fd7b89c)

Co-authored-by: Dan Kortschak <[email protected]>
chrisberkhout pushed a commit that referenced this pull request Jun 1, 2023
EvtFormatMessage appears to sometimes claim that more buffer was used
during a rendering call than was or exists, so do not use this value
except in the query to get the needed buffer size.
@reakaleek reakaleek mentioned this pull request Jul 19, 2023
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.9-candidate backport-v8.8.0 Automated backport with mergify bug needs_team Indicates that the issue/PR needs a Team:* label Winlogbeat
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants