linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Kinglong Mee <kinglongmee@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] NFSD: Decrease nfsd_users in nfsd_startup_generic fail
Date: Wed, 30 Jul 2014 10:16:48 -0400	[thread overview]
Message-ID: <20140730141648.GE26316@fieldses.org> (raw)
In-Reply-To: <53D8F26D.8070304@gmail.com>

Thanks!

On Wed, Jul 30, 2014 at 09:26:05PM +0800, Kinglong Mee wrote:
> If nfsd_startup_generic fail, nfsd_users isn't decreased right now.

Looks like that should only fail in out of memory cases?

> NFSD restarts will return 0 at the first nfsd_users checking,
> after that, nfs4_state_start_net() will meet a bad laundry_wq
> (I meet NULL), after nfsd4_grace timeout, the kernel will crash.

So this was introduced with 4539f14981ce02d48b212786a41c8bcfb62851b4
"nfsd: replace boolean nfsd_up flag by users counter".

--b.

> 
> Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
> ---
>  fs/nfsd/nfssvc.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/nfsd/nfssvc.c b/fs/nfsd/nfssvc.c
> index 5d026dc..752d56b 100644
> --- a/fs/nfsd/nfssvc.c
> +++ b/fs/nfsd/nfssvc.c
> @@ -221,7 +221,8 @@ static int nfsd_startup_generic(int nrservs)
>  	 */
>  	ret = nfsd_racache_init(2*nrservs);
>  	if (ret)
> -		return ret;
> +		goto dec_users;
> +
>  	ret = nfs4_state_start();
>  	if (ret)
>  		goto out_racache;
> @@ -229,6 +230,8 @@ static int nfsd_startup_generic(int nrservs)
>  
>  out_racache:
>  	nfsd_racache_shutdown();
> +dec_users:
> +	nfsd_users--;
>  	return ret;
>  }
>  
> -- 
> 1.9.3
> 

  reply	other threads:[~2014-07-30 14:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30 13:26 [PATCH] NFSD: Decrease nfsd_users in nfsd_startup_generic fail Kinglong Mee
2014-07-30 14:16 ` J. Bruce Fields [this message]
2014-07-31 12:56   ` Kinglong Mee
2014-08-01 20:29     ` J. Bruce Fields

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=20140730141648.GE26316@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=kinglongmee@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    /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).