mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git fixes
Date: Thu, 27 Apr 2017 08:34:18 +0100	[thread overview]
Message-ID: <20170427073418.GC29622@ZenIV.linux.org.uk> (raw)

	* 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(-)

             reply	other threads:[~2017-04-27  7:34 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-27  7:34 Al Viro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-10 20:27 Al Viro
2023-03-11  4:52 ` pr-tracker-bot
2021-01-17  3:21 Al Viro
2021-01-17 20:20 ` pr-tracker-bot
2020-10-11 18:06 Al Viro
2020-10-11 18:23 ` pr-tracker-bot
2020-04-28 21:18 Al Viro
2020-04-28 21:45 ` pr-tracker-bot
2020-03-12 22:37 Al Viro
2020-03-12 23:00 ` pr-tracker-bot
2020-02-24  0:22 Al Viro
2020-02-24 20:25 ` pr-tracker-bot
2020-01-26 18:25 Al Viro
2020-01-26 19:30 ` pr-tracker-bot
2019-11-24 20:05 Al Viro
2019-11-25  0:35 ` pr-tracker-bot
2019-11-15  0:50 Al Viro
2019-11-15 17:35 ` pr-tracker-bot
2019-05-05  2:18 Al Viro
2019-05-05 22:10 ` pr-tracker-bot
2019-03-03  3:42 Al Viro
2019-03-03 20:21 ` Linus Torvalds
2019-03-04 21:30 ` pr-tracker-bot
2018-11-30  5:15 Al Viro
2018-11-30 21:00 ` pr-tracker-bot
2018-03-16  1:41 Al Viro
2017-10-22  0:12 Al Viro
2017-10-11  4:54 Al Viro
2017-10-11 17:47 ` Vitaly Mayatskikh
2017-05-21 17:24 Al Viro
2016-07-12  5:16 Al Viro
2016-07-01 20:51 Al Viro
2015-12-06 17:40 Al Viro
2015-11-25 23:08 Al Viro
2015-01-25  2:39 Al Viro
2014-11-22  4:43 Al Viro
2014-11-06  5:04 Al Viro
2013-11-11 16:30 [git pull] vfs.git Al Viro
2013-11-13 13:17 ` [git pull] vfs.git fixes Al Viro

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=20170427073418.GC29622@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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