linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas-Mich Richter <tmricht@linux.ibm.com>
Cc: brueckner@linux.vnet.ibm.com, schwidefsky@de.ibm.com,
	heiko.carstens@de.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] inode: debugfs_create_dir uses mode permission from parent
Date: Fri, 27 Apr 2018 12:06:00 +0200	[thread overview]
Message-ID: <20180427100600.GB12941@kroah.com> (raw)
In-Reply-To: <504bade7-7b06-c9d4-e4e2-736b9ee5a313@linux.ibm.com>

On Fri, Apr 27, 2018 at 11:14:26AM +0200, Thomas-Mich Richter wrote:
> On 04/27/2018 10:27 AM, Greg KH wrote:
> > On Fri, Apr 27, 2018 at 10:07:12AM +0200, Thomas Richter wrote:
> >> Currently function debugfs_create_dir() creates a new
> >> directory in the debugfs (usually mounted /sys/kernel/debug)
> >> with permission rwxr-xr-x. This is hard coded.
> >>
> >> Change this to use the parent directory permission.
> >>
> >> Fixes: edac65eaf8d5c ("debugfs: take mode-dependent parts of debugfs_get_inode() into callers")
> >> Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
> >> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> >> ---
> >>  fs/debugfs/inode.c | 5 ++++-
> >>  1 file changed, 4 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/fs/debugfs/inode.c b/fs/debugfs/inode.c
> >> index 13b01351dd1c..80618330d86a 100644
> >> --- a/fs/debugfs/inode.c
> >> +++ b/fs/debugfs/inode.c
> >> @@ -512,7 +512,10 @@ struct dentry *debugfs_create_dir(const char *name, struct dentry *parent)
> >>  	if (unlikely(!inode))
> >>  		return failed_creating(dentry);
> >>  
> >> -	inode->i_mode = S_IFDIR | S_IRWXU | S_IRUGO | S_IXUGO;
> >> +	if(!parent)
> >> +		parent = debugfs_mount->mnt_root;
> >> +	inode->i_mode = S_IFDIR | (d_inode(parent)->i_mode
> >> +				   & (S_IRWXU | S_IRWXG));
> >>  	inode->i_op = &simple_dir_inode_operations;
> >>  	inode->i_fop = &simple_dir_operations;
> >>  
> > 
> > This looks ok, but is it going to change the permissions of existing
> > stuff in ways that might breaks things, right?
> 
> Right, but debugfs is usually mounted on /sys/kernel/debug with
> permissions rwx to root owner. It can be changed after the mount, of course.
> Unless this is done, the directory permissions for /sys/kernel/debug
> will stop any descend regardless  of the subdirectory permissions.
> 
> > 
> > Have you done a before/after comparison?
> 
> I have tested this patch on my Linux 4.17.0rc2 kernel on s390.
> That worked well, I have not tested other systems.

What do you mean by "worked well"?  What were the full tree differences
between before and after?  You should be able to get this by using:
	tree -dp /sys/kernel/debug/
and then doing a diff on the two files.

thanks,

greg k-h

  reply	other threads:[~2018-04-27 10:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-27  8:07 [PATCH] inode: debugfs_create_dir uses mode permission from parent Thomas Richter
2018-04-27  8:27 ` Greg KH
2018-04-27  9:14   ` Thomas-Mich Richter
2018-04-27 10:06     ` Greg KH [this message]
2018-04-27 11:30       ` Thomas-Mich Richter
2018-04-27 11:47         ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180427100600.GB12941@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=brueckner@linux.vnet.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=tmricht@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).