iovisor / iovisor/bcc

not working when CONFIG_TRACEFS_DISABLE_AUTOMOUNT enabled

Open
#4,043 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
22.7k
Forks
4.1k
Avg merge
10d 4h
Merged PRs (30d)
3

Description

when CONFIG_TRACEFS_DISABLE_AUTOMOUNT is enabled in kernel config, the kernel won't automount tracefs when mount debugfs, so the `/sys/kernel/debug/tracing` is not exist, we should use `/sys/kernel/tracing` instead.

Here is the kernel chanelog: https://osdn.net/projects/android-x86/scm/git/kernel/commits/412bd71850dbd2d78ee3bbd1e43e3ebe3c9bd819

And the mount:

```
oriole:/ # mount -t tracefs
tracefs on /sys/kernel/tracing type tracefs (rw,seclabel,relatime,gid=3012)
```

When we umount debugfs and remount, the `/sys/kernel/debug/tracing` is not exist, and we can't mount the tracefs to `/sys/kernel/debug/tracing` becase there isn't any mount point.

I replace all `/sys/kernel/debug/tracing` to `/sys/kernel/tracing` in the source code and compile it again can make it work.

Contributor guide

No contributing guide indexed for this repository

Research direction

Search the C source for references to `/sys/kernel/debug/tracing` and inspect the tracefs/debugfs mount handling. Reproduce the issue with CONFIG_TRACEFS_DISABLE_AUTOMOUNT enabled, then verify tracing still works through `/sys/kernel/tracing` after debugfs is unmounted and remounted.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.