All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Kinglong Mee <kinglongmee@gmail.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org,
	Trond Myklebust <trond.myklebust@primarydata.com>
Subject: Re: [PATCH 6/6 v9] nfsd: Allows user un-mounting filesystem where nfsd exports base on
Date: Wed, 19 Aug 2015 13:54:56 +1000	[thread overview]
Message-ID: <20150819135456.0294a334@noble> (raw)
In-Reply-To: <55D2DD8F.6070501@gmail.com>

On Tue, 18 Aug 2015 15:23:59 +0800 Kinglong Mee <kinglongmee@gmail.com>
wrote:

>  static void expkey_put(struct kref *ref)
>  {
>  	struct svc_expkey *key = container_of(ref, struct svc_expkey, h.ref);
>  
>  	if (test_bit(CACHE_VALID, &key->h.flags) &&
> -	    !test_bit(CACHE_NEGATIVE, &key->h.flags))
> -		path_put(&key->ek_path);
> -	auth_domain_put(key->ek_client);
> -	kfree(key);
> +	    !test_bit(CACHE_NEGATIVE, &key->h.flags)) {
> +		rcu_read_lock();
> +		if (path_put_unpin(&key->ek_path, &key->ek_pin))
> +			return ;
> +	}

That rcu_read_lock() is unbalanced and not needed.

Comment applies below in svc_export code too.


> +static void expkey_pin_kill(struct fs_pin *pin)
> +{
> +	struct svc_expkey *key = container_of(pin, struct svc_expkey, ek_pin);
> +	cache_delete_entry(key->cd, &key->h);
> +	/* Must call pin_kill to wait the last reference be put */
> +	pin_kill(&key->ek_pin);
> +	expkey_destroy(key);
>  }

This, on the other hand, needs rcu_read_lock().  pin_kill() expected
rcu to be readlocked, and will drop the lock.

Same comment for svc_export code.


Did you test with lockdep enabled?  That should have caught these
issues.

Otherwise it looks good.

Reviewed-by: NeilBrown <neilb@suse.com>

Thanks,
NeilBrown

WARNING: multiple messages have this Message-ID (diff)
From: NeilBrown <neilb-IBi9RG/b67k@public.gmane.org>
To: Kinglong Mee <kinglongmee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "J. Bruce Fields"
	<bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>,
	Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>,
	"linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Trond Myklebust
	<trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
Subject: Re: [PATCH 6/6 v9] nfsd: Allows user un-mounting filesystem where nfsd exports base on
Date: Wed, 19 Aug 2015 13:54:56 +1000	[thread overview]
Message-ID: <20150819135456.0294a334@noble> (raw)
In-Reply-To: <55D2DD8F.6070501-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On Tue, 18 Aug 2015 15:23:59 +0800 Kinglong Mee <kinglongmee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:

>  static void expkey_put(struct kref *ref)
>  {
>  	struct svc_expkey *key = container_of(ref, struct svc_expkey, h.ref);
>  
>  	if (test_bit(CACHE_VALID, &key->h.flags) &&
> -	    !test_bit(CACHE_NEGATIVE, &key->h.flags))
> -		path_put(&key->ek_path);
> -	auth_domain_put(key->ek_client);
> -	kfree(key);
> +	    !test_bit(CACHE_NEGATIVE, &key->h.flags)) {
> +		rcu_read_lock();
> +		if (path_put_unpin(&key->ek_path, &key->ek_pin))
> +			return ;
> +	}

That rcu_read_lock() is unbalanced and not needed.

Comment applies below in svc_export code too.


> +static void expkey_pin_kill(struct fs_pin *pin)
> +{
> +	struct svc_expkey *key = container_of(pin, struct svc_expkey, ek_pin);
> +	cache_delete_entry(key->cd, &key->h);
> +	/* Must call pin_kill to wait the last reference be put */
> +	pin_kill(&key->ek_pin);
> +	expkey_destroy(key);
>  }

This, on the other hand, needs rcu_read_lock().  pin_kill() expected
rcu to be readlocked, and will drop the lock.

Same comment for svc_export code.


Did you test with lockdep enabled?  That should have caught these
issues.

Otherwise it looks good.

Reviewed-by: NeilBrown <neilb-IBi9RG/b67k@public.gmane.org>

Thanks,
NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-08-19  3:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18  7:17 [PATCH 0/6 v9] NFSD: Pin to vfsmount for nfsd exports cache Kinglong Mee
2015-08-18  7:17 ` Kinglong Mee
2015-08-18  7:18 ` [PATCH 1/6 v9] fs-pin: allow pin_remove() to be called other than from->kill() Kinglong Mee
2015-08-18  7:18   ` Kinglong Mee
2015-08-18  7:19 ` [PATCH 2/6] fs_pin: Export functions for specific filesystem Kinglong Mee
2015-08-18  7:19   ` Kinglong Mee
2015-08-18  7:20 ` [PATCH 3/6 v9] path: New helpers path_get_pin/path_put_unpin for path pin Kinglong Mee
2015-08-18  7:20   ` Kinglong Mee
2015-08-18  7:21 ` [PATCH 4/6 v9] fs: New helper legitimize_mntget() for getting a legitimize mnt Kinglong Mee
2015-08-18  7:21   ` Kinglong Mee
2015-08-19  4:56   ` NeilBrown
2015-08-19  4:56     ` NeilBrown
2015-08-19  5:02     ` Al Viro
2015-08-27 23:02       ` Kinglong Mee
2015-08-27 23:02         ` Kinglong Mee
2015-08-18  7:22 ` [PATCH 5/6 v9] sunrpc: New helper cache_delete_entry for deleting cache_head directly Kinglong Mee
2015-08-18  7:22   ` Kinglong Mee
2015-08-18  7:23 ` [PATCH 6/6 v9] nfsd: Allows user un-mounting filesystem where nfsd exports base on Kinglong Mee
2015-08-18  7:23   ` Kinglong Mee
2015-08-19  3:54   ` NeilBrown [this message]
2015-08-19  3:54     ` NeilBrown
2015-08-19  4:50   ` Al Viro
2015-08-19  4:50     ` Al Viro
2015-08-27 23:15     ` Kinglong Mee
2015-08-27 23:15       ` Kinglong Mee
2015-08-18  7:24 ` [PATCH 2/6 v9] fs_pin: Export functions for specific filesystem Kinglong Mee
2015-08-18  7:24   ` Kinglong Mee

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=20150819135456.0294a334@noble \
    --to=neilb@suse.com \
    --cc=bfields@fieldses.org \
    --cc=kinglongmee@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.