From: Sasha Levin <sashal@kernel.org>
To: Qian Lu <luqia@amazon.com>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org,
bfields@redhat.com, ctracy@engr.scu.edu
Subject: Re: Request for inclusion on linux-4.14.y
Date: Sun, 28 Jul 2019 11:04:25 -0400 [thread overview]
Message-ID: <20190728150425.GD8637@sasha-vm> (raw)
In-Reply-To: <20190726213635.GB1900@dev-dsk-luqia-2a-c7316a94.us-west-2.amazon.com>
On Fri, Jul 26, 2019 at 02:36:35PM -0700, Qian Lu wrote:
>Hello Greg,
>
>Can you please consider including the following patches in the stable
>linux-4.14.y branch?
>
>An NFS server accepts only a limited number of concurrent v4.1+ mounts. Once
>that limit is reached, on the affected client side, mount.nfs appears to hang to
>keep reissuing CREATE_SESSION calls until one of them succeeds. This is to bump
>the limit, also return smaller ca_maxrequests as the limit approaches instead of
>waiting till we have to fail CREATE_SESSION completely.
>
>44d8660d3bb0("nfsd: increase DRC cache limit")
>de766e570413("nfsd: give out fewer session slots as limit approaches")
>c54f24e338ed("nfsd: fix performance-limiting session calculation")
I've queued these 3 for 4.14 and older.
Note that c54f24e338ed has a fix: 3b2d4dcf71c4a ("nfsd: Fix overflow
causing non-working mounts on 1 TB machines") which was queued as well.
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-07-28 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 21:36 Request for inclusion on linux-4.14.y Qian Lu
2019-07-28 15:04 ` Sasha Levin [this message]
2019-07-29 19:58 ` J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2019-07-26 18:17 Qian Lu
2019-07-28 14:18 ` Sasha Levin
2018-09-19 22:37 Alakesh Haloi
2018-09-20 5:24 ` 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=20190728150425.GD8637@sasha-vm \
--to=sashal@kernel.org \
--cc=bfields@redhat.com \
--cc=ctracy@engr.scu.edu \
--cc=gregkh@linuxfoundation.org \
--cc=luqia@amazon.com \
--cc=stable@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 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.