iotracing: refactor file path handling to support multiple directories#99
Merged
hao022 merged 1 commit intoccfos:mainfrom Jan 10, 2026
Merged
iotracing: refactor file path handling to support multiple directories#99hao022 merged 1 commit intoccfos:mainfrom
hao022 merged 1 commit intoccfos:mainfrom
Conversation
sancppp
force-pushed
the
dir_resolution
branch
from
e0bd97d to
013d0e6
Compare
Signed-off-by: Zhenxiong Tian <[email protected]>
sancppp
force-pushed
the
dir_resolution
branch
from
013d0e6 to
8819f7a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request refactors how file path information is captured and represented in the I/O tracing code, both in the eBPF program (
iotracing.c) and in the Go code that consumes its data (iotracing.go). Instead of storing only a few individual directory names, the code now captures a configurable depth of the file path in a more flexible array structure, and reconstructs the full path accordingly.Before:
After:
The next step could be to further refactor the parsing and storage of file paths in an ebpf map to prevent kernel stack limits