linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git - misc bits and pieces
Date: Thu, 1 Nov 2018 23:49:46 +0000	[thread overview]
Message-ID: <20181101234946.GV32577@ZenIV.linux.org.uk> (raw)

	No common topic, really - a handful of assorted stuff; the least
trivial bits are Mark's dedupe patches.  After that the only thing remaining
in for-next would be work.mount...

The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:

  Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc

for you to fetch changes up to 3642b29a63674020401e41185ed5b0e3c056ab4a:

  fs/exofs: only use true/false for asignment of bool type variable (2018-10-18 02:04:59 -0400)

----------------------------------------------------------------
Al Viro (2):
      ext4: don't open-code ERR_CAST
      ntfs: don't open-code ERR_CAST

Chengguang Xu (2):
      fs/exofs: fix potential memory leak in mount option parsing
      fs/exofs: only use true/false for asignment of bool type variable

Mark Fasheh (2):
      vfs: allow dedupe of user owned read-only files
      vfs: dedupe should return EPERM if permission is not granted

Yue Haibing (1):
      iomap: remove duplicated include from iomap.c

nixiaoming (1):
      Delete invalid assignment statements in do_sendfile

 fs/exofs/super.c |  7 +++++--
 fs/ext4/ialloc.c |  2 +-
 fs/ext4/namei.c  |  4 ++--
 fs/iomap.c       |  1 -
 fs/ntfs/namei.c  |  2 +-
 fs/read_write.c  | 19 ++++++++++++++++---
 6 files changed, 25 insertions(+), 10 deletions(-)

             reply	other threads:[~2018-11-02  8:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01 23:49 Al Viro [this message]
2018-11-02  3:20 ` [git pull] vfs.git - misc bits and pieces Linus Torvalds

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=20181101234946.GV32577@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@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).