Re: [PATCH 2/2] tracefs: Only clobber mode/uid/gid on remount if asked

[Steven Rostedt]

On Fri, 26 Aug 2022 17:44:17 -0700
Brian Norris <briannorris@xxxxxxxxxxxx> wrote:

> Users may have explicitly configured their tracefs permissions; we
> shouldn't overwrite those just because a second mount appeared.
> 
> Only clobber if the options were provided at mount time.
> 
> Note: the previous behavior was especially surprising in the presence of
> automounted /sys/kernel/debug/tracing/.
> 
>   # Don't change /sys/kernel/tracing/ permissions on automount.
>   umount /sys/kernel/debug/tracing/
>   stat /sys/kernel/debug/tracing/.
> 
>   # Don't change /sys/kernel/tracing/ permissions.
>   mount -t tracefs none /mnt/foo
> 
>   # Change /sys/kernel/tracing/ mode and uid, but not gid.
>   mount -t tracefs -o uid=bar,mode=0750 none /mnt/baz
> 

The above text doesn't make sense. Is the comments what you are doing or
what the system is doing? If it is what the system is doing, please show
the output of the stat command and how it is doing something unexpected.

Can you show the example of what is wrong, and what you expected to happen.
The above is just a bunch of commands, but does not display anything that
is incorrect.

> Signed-off-by: Brian Norris <briannorris@xxxxxxxxxxxx>
> ---
> I'm open to writing an LTP test case for this, if that seems like a good
> idea.

Yes, please add a test :-)

-- Steve

> 
>  fs/tracefs/inode.c | 31 +++++++++++++++++++++++--------
>  1 file changed, 23 insertions(+), 8 deletions(-)
> 
>