public inbox for linux-kernel@vger.kernel.org
 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] several vfs and fs fixes for 4.0
Date: Sun, 12 Apr 2015 05:06:20 +0100	[thread overview]
Message-ID: <20150412040620.GM889@ZenIV.linux.org.uk> (raw)

	Several AIO and OCFS2 fixes.  Please, pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus

Shortlog:
Al Viro (5):
      fix mremap() vs. ioctx_kill() race
      ioctx_alloc(): fix vma (and file) leak on failure
      [regression] ocfs2: do *not* increment ->ki_pos twice
      ocfs2_file_write_iter: keep return value and current position update in sync
      ocfs2: _really_ sync the right range

Diffstat:
 fs/aio.c           | 20 ++++++++++++++------
 fs/ocfs2/file.c    | 17 +++++++++++------
 include/linux/fs.h |  2 +-
 mm/mremap.c        | 10 ++++++++--
 4 files changed, 34 insertions(+), 15 deletions(-)

                 reply	other threads:[~2015-04-12  4:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20150412040620.GM889@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