interfaces: Add /sys/kernel/tracing to system-trace #16232
Conversation
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
github-actions
bot
added
the
Run only one system
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #16232 +/- ##
==========================================
+ Coverage 77.45% 77.46% +0.01%
==========================================
Files 1333 1333
Lines 181634 181617 -17
Branches 2398 2398
==========================================
+ Hits 140685 140694 +9
+ Misses 32427 32402 -25
+ Partials 8522 8521 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Sun Nov 2 22:43:40 UTC 2025 Failures:Executing:
Restoring:
|
Systemd has mounted tracefs under /sys/kernel/tracing since version 245 [0]. Simultaneously, the kernel started at version 4.1 to automount /sys/kernel/debug/tracing on access for backwards compatibiliy. The builtin system-trace currently only allows the old path. Applications exist who will assume /sys/kernel/tracing as the preferred location, only to fall back to /sys/kernel/debug/tracing if the path does not exist. Currently said applications will fail to work in snaps, because they will find /sys/kernel/tracing to exist only to fail later in execution when trying to access contents of files within. 0: systemd/systemd@aaaf42cb44d4 Signed-off-by: Frode Nordahl <[email protected]>
github-actions
bot
removed
the
Run only one system
fnordahl
force-pushed
the
fix-tracefs-path
branch
from
799164d to
3d0f442
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Systemd has mounted tracefs under /sys/kernel/tracing since version 245 [0]. Simultaneously, the kernel started at version 4.1 to automount /sys/kernel/debug/tracing on access for backwards compatibiliy.
The builtin system-trace currently only allows the old path.
Applications exist who will assume /sys/kernel/tracing as the preferred location, only to fall back to /sys/kernel/debug/tracing if the path does not exist.
Currently said applications will fail to work in snaps, because they will find /sys/kernel/tracing to exist only to fail later in execution when trying to access contents of files within.
0: systemd/systemd@aaaf42cb44d4
Thanks for helping us make a better snapd!
Have you signed the license agreement and read the contribution guide?