linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Al Viro <viro@ZenIV.linux.org.uk>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC][PATCH] fix breakage caused by d_find_alias() semantics change
Date: Mon, 14 May 2018 08:02:32 +1000	[thread overview]
Message-ID: <87h8nb8b9j.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20180513194829.GT30522@ZenIV.linux.org.uk>

[-- Attachment #1: Type: text/plain, Size: 2581 bytes --]

On Sun, May 13 2018, Al Viro wrote:

> On Sun, May 13, 2018 at 11:59:58AM -0700, Linus Torvalds wrote:
>> On Sun, May 13, 2018 at 11:56 AM Al Viro <viro@zeniv.linux.org.uk> wrote:
>> 
>> > The whole reason why that thing is getting a dentry is that some
>> filesystems
>> > really want a *connected* dentry for getxattr.  Sure, saner ones will be
>> > happy with disconnected dentry, but...
>> 
>> Can we just add a big comment to that effect?
>> 
>> Because I don't mind the complexity, but I do mind having code that _looks_
>> complex with no reason, where the natural reaction is "why is it bothering
>> being complex, when it could just do X".
>
> Point taken.  How about the following variant?
>
> diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c
> index 4cafe6a19167..398d165f884e 100644
> --- a/security/selinux/hooks.c
> +++ b/security/selinux/hooks.c
> @@ -1568,8 +1568,15 @@ static int inode_doinit_with_dentry(struct inode *inode, struct dentry *opt_dent
>  			/* Called from d_instantiate or d_splice_alias. */
>  			dentry = dget(opt_dentry);
>  		} else {
> -			/* Called from selinux_complete_init, try to find a dentry. */
> +			/*
> +			 * Called from selinux_complete_init, try to find a dentry.
> +			 * Some filesystems really want a connected one, so try
> +			 * that first.  We could split SECURITY_FS_USE_XATTR in
> +			 * two, depending upon that...
> +			 */

Could you say *which* file systems?  That would make it easier to
understand the bigger picture.

thanks,
NeilBrown


>  			dentry = d_find_alias(inode);
> +			if (!dentry)
> +				dentry = d_find_any_alias(inode);
>  		}
>  		if (!dentry) {
>  			/*
> @@ -1674,14 +1681,19 @@ static int inode_doinit_with_dentry(struct inode *inode, struct dentry *opt_dent
>  		if ((sbsec->flags & SE_SBGENFS) && !S_ISLNK(inode->i_mode)) {
>  			/* We must have a dentry to determine the label on
>  			 * procfs inodes */
> -			if (opt_dentry)
> +			if (opt_dentry) {
>  				/* Called from d_instantiate or
>  				 * d_splice_alias. */
>  				dentry = dget(opt_dentry);
> -			else
> +			} else {
>  				/* Called from selinux_complete_init, try to
> -				 * find a dentry. */
> +				 * find a dentry.  Some filesystems really want
> +				 * a connected one, so try that first.
> +				 */
>  				dentry = d_find_alias(inode);
> +				if (!dentry)
> +					dentry = d_find_any_alias(inode);
> +			}
>  			/*
>  			 * This can be hit on boot when a file is accessed
>  			 * before the policy is loaded.  When we load policy we

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2018-05-13 22:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-13 15:51 [RFC][PATCH] fix breakage caused by d_find_alias() semantics change Al Viro
2018-05-13 18:35 ` Linus Torvalds
2018-05-13 18:56   ` Al Viro
2018-05-13 18:59     ` Linus Torvalds
2018-05-13 19:48       ` Al Viro
2018-05-13 20:24         ` Linus Torvalds
2018-05-13 22:02         ` NeilBrown [this message]
2018-05-13 22:17           ` Al Viro

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=87h8nb8b9j.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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).