linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: [GIT PULL] Please pull NFS client changes
Date: Sun, 25 Nov 2018 03:04:11 +0000	[thread overview]
Message-ID: <adb722d9cf7e1d6d1a3290f0af044b948bc81511.camel@hammerspace.com> (raw)

Hi Linus,

The following changes since commit 9ff01193a20d391e8dbce4403dd5ef87c7eaaca6:

  Linux 4.20-rc3 (2018-11-18 13:33:44 -0800)

are available in the Git repository at:

  git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.20-4

for you to fetch changes up to bb21ce0ad227b69ec0f83279297ee44232105d96:

  flexfiles: use per-mirror specified stateid for IO (2018-11-22 14:04:55 -0500)

----------------------------------------------------------------
NFS client bugfixes for Linux 4.20

Highlights include:

Bugfixes:
 - Fix a NFSv4 state manager deadlock when returning a delegation
 - NFSv4.2 copy do not allocate memory under the lock
 - flexfiles: Use the correct stateid for IO in the tightly coupled case

----------------------------------------------------------------
Olga Kornievskaia (1):
      NFSv4.2 copy do not allocate memory under the lock

Tigran Mkrtchyan (1):
      flexfiles: use per-mirror specified stateid for IO

Trond Myklebust (1):
      NFSv4: Fix a NFSv4 state manager deadlock

 fs/nfs/callback_proc.c                    | 22 +++++++++++-----------
 fs/nfs/flexfilelayout/flexfilelayout.c    | 21 +++++++++------------
 fs/nfs/flexfilelayout/flexfilelayout.h    |  4 ++++
 fs/nfs/flexfilelayout/flexfilelayoutdev.c | 19 +++++++++++++++++++
 fs/nfs/nfs42proc.c                        | 19 ++++++++++---------
 fs/nfs/nfs4_fs.h                          |  2 ++
 fs/nfs/nfs4state.c                        | 16 +++++++++++-----
 7 files changed, 66 insertions(+), 37 deletions(-)
-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



             reply	other threads:[~2018-11-25  3:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-25  3:04 Trond Myklebust [this message]
2018-11-25 17:45 ` [GIT PULL] Please pull NFS client changes pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2022-04-08 17:30 Trond Myklebust
2022-04-08 17:46 ` pr-tracker-bot
2018-12-06 21:55 Trond Myklebust
2018-12-07 18:35 ` pr-tracker-bot
2018-01-30 14:39 Trond Myklebust
2017-10-09 17:35 Trond Myklebust
2016-01-14 21:09 Trond Myklebust
2015-09-07 20:59 Trond Myklebust
2015-09-08  1:59 ` Stephen Rothwell
2015-09-08  6:01   ` Christoph Hellwig
2015-09-11 16:27     ` Christoph Hellwig
2015-09-11 17:06       ` Trond Myklebust
2014-12-08  3:09 Trond Myklebust
2014-10-06 13:03 Trond Myklebust
2014-07-19 20:07 Trond Myklebust
2014-01-27 16:49 Trond Myklebust
2011-10-25 12:25 Trond Myklebust
2011-07-27 18:40 [GIT PULL] Please pull nfs " Trond Myklebust
2011-03-17 17:19 [GIT PULL] Please pull NFS " Trond Myklebust
2011-01-11 23:08 Trond Myklebust
2010-08-06 18:26 Trond Myklebust
2010-05-17 22:28 Trond Myklebust
2010-05-18  8:59 ` Lukas Hejtmanek

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=adb722d9cf7e1d6d1a3290f0af044b948bc81511.camel@hammerspace.com \
    --to=trondmy@hammerspace.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).