mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anna Schumaker <schumaker.anna@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Please pull additional NFS client fixes for 5.0
Date: Fri, 15 Feb 2019 16:47:50 -0500	[thread overview]
Message-ID: <39718a97aca3b96d016069ea46371b193f8ac41a.camel@gmail.com> (raw)

Hi Linus,

The following changes since commit 8fc75bed96bb94e23ca51bd9be4daf65c57697bf:

  NFS: Fix up return value on fatal errors in nfs_page_async_flush() (2019-01-29 
16:33:24 -0500)

are available in the Git repository at:

  git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-5.0-4

for you to fetch changes up to d2ceb7e57086750ea6198a31fd942d98099a0786:

  NFS: Don't use page_file_mapping after removing the page (2019-02-12 15:56:28
-0500)

----------------------------------------------------------------
Three fixes this time.  Nicolas's is for xprtrdma completion vector allocation
on single-core systems.  Greg's adds an error check when allocating a debugfs
dentry.  And Ben's is an additional fix for nfs_page_async_flush() to prevent
pages from accidentally getting truncated.

Have a good weekend!
Anna
----------------------------------------------------------------
Benjamin Coddington (1):
      NFS: Don't use page_file_mapping after removing the page

Greg Kroah-Hartman (1):
      rpc: properly check debugfs dentry before using it

Nicolas Morey-Chaisemartin (1):
      xprtrdma: Make sure Send CQ is allocated on an existing compvec

 fs/nfs/write.c              | 11 ++++++-----
 net/sunrpc/debugfs.c        |  2 +-
 net/sunrpc/xprtrdma/verbs.c |  3 ++-
 3 files changed, 9 insertions(+), 7 deletions(-)


             reply	other threads:[~2019-02-15 21:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15 21:47 Anna Schumaker [this message]
2019-02-17  1:50 ` 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=39718a97aca3b96d016069ea46371b193f8ac41a.camel@gmail.com \
    --to=schumaker.anna@gmail.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

Powered by JetHome