Skip to content

kmsg: Log the raw buffer if we fail to parse (#1704) #1709

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

Merged
merged 2 commits into from
Jul 16, 2025

Conversation

smalis-msft
Copy link
Contributor

We've seen a crash here in the wild, but haven't yet figured out what exactly is failing to parse. Add some more logging so we can hopefully get this if it happens again.

Cherry-pick of #1704

We've seen a crash here in the wild, but haven't yet figured out what
exactly is failing to parse. Add some more logging so we can hopefully
get this if it happens again.
@smalis-msft smalis-msft requested a review from a team as a code owner July 16, 2025 18:41
@github-actions github-actions bot added the release_2505 Targets the release/2505 branch. label Jul 16, 2025
@smalis-msft smalis-msft enabled auto-merge (squash) July 16, 2025 19:13
@smalis-msft smalis-msft merged commit 4f526e8 into microsoft:release/2505 Jul 16, 2025
24 checks passed
@smalis-msft smalis-msft deleted the kmsg-log-2505 branch July 16, 2025 19:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_2505 Targets the release/2505 branch.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants