Skip to content

[bug]Message fields incorrectly deleted from GCS logs - #2844

Merged
helsaawy merged 1 commit into
microsoft:mainfrom
helsaawy:kmsg
Jul 30, 2026
Merged

[bug]Message fields incorrectly deleted from GCS logs#2844
helsaawy merged 1 commit into
microsoft:mainfrom
helsaawy:kmsg

Conversation

@helsaawy

Copy link
Copy Markdown
Contributor

Fix bug in (*GCSLogEntry).UnmarshalJSON where [mM]essage fields where always deleted, even in non-ETW cases.
This prevented the actual kmsg logs (where are added as message in log entries) from being correctly logged by the shim.

Also:

  • remove trailing spaces in init dmesg logs.
  • increase /dev/kmsg read buffer and add comments about size.
  • trim trailing spaces (and newline) from parsed kmsg messages.

Fix bug in `(*GCSLogEntry).UnmarshalJSON` where `[mM]essage` fields
where always deleted, even in non-ETW cases.
This prevented the actual `kmsg` logs (where are added as `message` in
log entries) from being correctly logged by the shim.

Also:
 - remove trailing spaces in `init` dmesg logs.
 - increase `/dev/kmsg` read buffer and add comments about size.
 - trim trailing spaces (and newline) from parsed kmsg messages.

Signed-off-by: Hamza El-Saawy <hamzaelsaawy@microsoft.com>
@helsaawy
helsaawy requested a review from a team as a code owner July 30, 2026 16:00
@helsaawy
helsaawy merged commit a9fcaca into microsoft:main Jul 30, 2026
20 checks passed
@helsaawy
helsaawy deleted the kmsg branch July 30, 2026 17:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants