From: "Schumaker, Anna" <Anna.Schumaker@netapp.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 bugfixes for 5.0-rc5
Date: Thu, 31 Jan 2019 18:12:24 +0000 [thread overview]
Message-ID: <c00eb546108828e6f73a2aeca5efd041f66593a1.camel@netapp.com> (raw)
Hi Linus,
The following changes since commit deaa5c96c2f7e8b934088a1e70a0fe8797bd1149:
SUNRPC: Address Kerberos performance/behavior regression (2019-01-15 15:36:41
-0500)
are available in the Git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git tags/nfs-for-5.0-3
for you to fetch changes up to 8fc75bed96bb94e23ca51bd9be4daf65c57697bf:
NFS: Fix up return value on fatal errors in nfs_page_async_flush() (2019-01-29
16:33:24 -0500)
----------------------------------------------------------------
This pull request addresses two bugs, one in the error code handling of
nfs_page_async_flush() and one to fix a potential NULL pointer dereference
in nfs_parse_devname().
Thanks,
Anna
----------------------------------------------------------------
Trond Myklebust (1):
NFS: Fix up return value on fatal errors in nfs_page_async_flush()
Yao Liu (1):
nfs: Fix NULL pointer dereference of dev_name
fs/nfs/super.c | 5 +++++
fs/nfs/write.c | 9 +++++----
2 files changed, 10 insertions(+), 4 deletions(-)
next reply other threads:[~2019-01-31 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 18:12 Schumaker, Anna [this message]
2019-01-31 19:30 ` [GIT PULL] Please pull NFS client bugfixes for 5.0-rc5 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=c00eb546108828e6f73a2aeca5efd041f66593a1.camel@netapp.com \
--to=anna.schumaker@netapp.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).