[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20170427073418.GC29622@ZenIV.linux.org.uk>
Date: Thu, 27 Apr 2017 08:34:18 +0100
From: Al Viro <viro@...IV.linux.org.uk>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: [git pull] vfs.git fixes
* fix orangefs handling of faults on write() - I'd missed that one
back when orangefs was going through review.
* readdir counterpart of "9p: cope with bogus responses from server
in p9_client_{read,write}" - server might be lying or broken, and we'd better
not overrun the kmalloc'ed buffer we are copying the results into.
* NFS O_DIRECT read/write can leave iov_iter advanced by too much;
that's what had been causing iov_iter_pipe() warnings davej had been seeing.
* statx_timestamp.tv_nsec type fix (s32 -> u32). That one really
should go in before 4.11.
The following changes since commit 4f7d029b9bf009fbee76bb10c0c4351a1870d2f3:
Linux 4.11-rc7 (2017-04-16 13:00:18 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
for you to fetch changes up to 1741937d475d91ed95abb37f07e8571e23b9a7fe:
uapi: change the type of struct statx_timestamp.tv_nsec to unsigned (2017-04-26 21:19:05 -0400)
----------------------------------------------------------------
Al Viro (3):
orangefs_bufmap_copy_from_iovec(): fix EFAULT handling
p9_client_readdir() fix
fix nfs O_DIRECT advancing iov_iter too much
Dmitry V. Levin (1):
uapi: change the type of struct statx_timestamp.tv_nsec to unsigned
fs/nfs/direct.c | 27 ++++++++++++++++++---------
fs/orangefs/orangefs-bufmap.c | 4 +---
include/uapi/linux/stat.h | 8 ++------
net/9p/client.c | 4 ++++
4 files changed, 25 insertions(+), 18 deletions(-)
Powered by blists - more mailing lists