On Mon, 30 Jan 2023 12:03:52 -0800 Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx> wrote: > > > > > > So this change will break the tests. We cannot do it. > > > > Could we add a way to try to mount it? > > > > If anything, the tests should not have the path hard coded. It should then > > look to see if it is mounted and use the path that is found. Otherwise it > > should try mounting it at the correct location. > > > > Feel free to take the code from libtracefs (and modify it): > > > > https://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git/tree/src/tracefs-utils.c#n89 > > > > It will make the test code much more robust. > > The point is not about tests. The point is that this change might break > some users that are working today with /sys/kernel/debug/tracing. > It also might be mounted differently. > For example from another system: > cat /proc/mounts|grep trace > tracefs /sys/kernel/tracing tracefs rw,nosuid,nodev,noexec,relatime 0 0 > tracefs /sys/kernel/debug/tracing tracefs rw,relatime 0 0 Yes, and the code works when it's mounted multiple times. > > So I suggest leaving the code as-is. Why? I want to make /sys/kernel/debug/tracing deprecated. It's a hack to not break old code. I've had complaints about that hack, and there's even systems that disable the auto mounting (that is, /sys/kernel/debug/tracing would not exist in such configs) This was never expected to be a permanent solution. If anything, leaving hardcoded calls like that forces the user to mount debugfs when they may not want to. The entire point of tracefs was to allow users to have access to the trace events without having to expose debugfs and all the crud it brings with it. This was requested several times before it was added. What is your technical reason for not modifying the code to look for tracefs in /sys/kernel/tracing and if it's not there try /sys/kernel/debug/tracing, and if both are not found, try mounting it. That change is not hard and makes the code much more robust and does not break anything. -- Steve
