From: Anna Schumaker <schumaker.anna@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: [GIT PULL] Please pull NFS Client Bugfixes for Linux 5.10-rc4
Date: Thu, 12 Nov 2020 12:15:22 -0500 [thread overview]
Message-ID: <CAFX2Jfnq+spZtxSbsy+tiUPgcYP4pHCJ_d2BGTW4TTQKchgJpQ@mail.gmail.com> (raw)
Hi Linus,
The following changes since commit 3cea11cd5e3b00d91caf0b4730194039b45c5891:
Linux 5.10-rc2 (2020-11-01 14:43:51 -0800)
are available in the Git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-5.10-2
for you to fetch changes up to 11decaf8127b035242cb55de2fc6946f8961f671:
NFS: Remove unnecessary inode lock in nfs_fsync_dir() (2020-11-12
10:41:26 -0500)
----------------------------------------------------------------
One stable fix and a few other smaller fixes this time around:
- Stable fixes:
- Fix failure to unregister shrinker
- Other fixes:
- Fix unnecessary locking to clear up some contention
- Fix listxattr receive buffer size
- Fix default mount options for nfsroot
Thanks,
Anna
----------------------------------------------------------------
Chuck Lever (1):
NFS: Fix listxattr receive buffer size
Helge Deller (1):
nfsroot: Default mount option should ask for built-in NFS version
J. Bruce Fields (1):
NFSv4.2: fix failure to unregister shrinker
Trond Myklebust (2):
NFS: Remove unnecessary inode locking in nfs_llseek_dir()
NFS: Remove unnecessary inode lock in nfs_fsync_dir()
fs/nfs/dir.c | 15 +++++----------
fs/nfs/nfs42xattr.c | 2 ++
fs/nfs/nfs42xdr.c | 4 ++--
fs/nfs/nfsroot.c | 6 ++++++
4 files changed, 15 insertions(+), 12 deletions(-)
next reply other threads:[~2020-11-12 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 17:15 Anna Schumaker [this message]
2020-11-12 22:11 ` [GIT PULL] Please pull NFS Client Bugfixes for Linux 5.10-rc4 pr-tracker-bot
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=CAFX2Jfnq+spZtxSbsy+tiUPgcYP4pHCJ_d2BGTW4TTQKchgJpQ@mail.gmail.com \
--to=schumaker.anna@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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).