All of lore.kernel.org
 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 fixes
Date: Mon, 21 May 2018 19:39:52 +0100	[thread overview]
Message-ID: <20180521183952.GC30522@ZenIV.linux.org.uk> (raw)

	Assorted fixes all over the place.  BTW, what is the preferred way
of sending a pull request on a series where an old commit has grown an
ACKed-by?  I've moved original branch to #fixes-old, git commit --amend
on commit[s] in question and rebased the tail of the series on top of that;
all trees involved are identical to ones in matching commits in original
branch, so all testing results (including integration in -next, etc.) are
still valid.  Is that approach OK with you?  Technically it is a rebase,
but it seems that none of the usual objections apply here...

The following changes since commit 16a34adb9392b2fe4195267475ab5b472e55292c:

  Don't leak MNT_INTERNAL away from internal mounts (2018-04-19 23:52:15 -0400)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git fixes

for you to fetch changes up to baf10564fbb66ea222cae66fbff11c444590ffd9:

  aio: fix io_destroy(2) vs. lookup_ioctx() race (2018-05-21 14:30:11 -0400)

----------------------------------------------------------------
Al Viro (11):
      do d_instantiate/unlock_new_inode combinations safely
      fix breakage caused by d_find_alias() semantics change
      affs_lookup(): close a race with affs_remove_link()
      affs_lookup: switch to d_splice_alias()
      befs_lookup(): use d_splice_alias()
      kernfs: deal with kernfs_fill_super() failures
      unfuck sysfs_mount()
      cachefiles: vfs_mkdir() might succeed leaving dentry negative unhashed
      nfsd: vfs_mkdir() might succeed leaving dentry negative unhashed
      ext2: fix a block leak
      aio: fix io_destroy(2) vs. lookup_ioctx() race

Dave Chinner (1):
      fs: don't scan the inode cache before SB_BORN is set

Ilya Dryomov (2):
      iov_iter: fix return type of __pipe_get_pages()
      iov_iter: fix memory leak in pipe_get_pages_alloc()

Joe Perches (1):
      cramfs: Fix IS_ENABLED typo

 fs/affs/namei.c          | 15 +++++++++------
 fs/aio.c                 |  4 ++--
 fs/befs/linuxvfs.c       | 17 +++++------------
 fs/btrfs/inode.c         | 16 ++++------------
 fs/cachefiles/namei.c    | 10 ++++++++++
 fs/cramfs/inode.c        |  2 +-
 fs/dcache.c              | 22 ++++++++++++++++++++++
 fs/ecryptfs/inode.c      |  3 +--
 fs/ext2/inode.c          | 10 ----------
 fs/ext2/namei.c          |  6 ++----
 fs/ext4/namei.c          |  6 ++----
 fs/f2fs/namei.c          | 12 ++++--------
 fs/jffs2/dir.c           | 12 ++++--------
 fs/jfs/namei.c           | 12 ++++--------
 fs/kernfs/mount.c        |  1 +
 fs/nfsd/vfs.c            | 22 ++++++++++++++++++++++
 fs/nilfs2/namei.c        |  6 ++----
 fs/orangefs/namei.c      |  9 +++------
 fs/reiserfs/namei.c      | 12 ++++--------
 fs/super.c               | 30 ++++++++++++++++++++++++------
 fs/sysfs/mount.c         |  6 +++---
 fs/udf/namei.c           |  6 ++----
 fs/ufs/namei.c           |  6 ++----
 include/linux/dcache.h   |  1 +
 lib/iov_iter.c           |  4 ++--
 security/selinux/hooks.c | 20 ++++++++++++++++----
 26 files changed, 152 insertions(+), 118 deletions(-)

             reply	other threads:[~2018-05-21 18:39 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21 18:39 Al Viro [this message]
2018-05-21 18:59 ` [git pull] vfs.git fixes Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2024-08-01 19:55 Al Viro
2024-08-02 16:53 ` pr-tracker-bot
2024-02-25  6:59 Al Viro
2024-02-25 17:58 ` pr-tracker-bot
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-08-12 17:44 Al Viro
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
2017-04-27  7:34 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=20180521183952.GC30522@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.