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-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs pile 3/many...
Date: Tue, 10 Sep 2013 17:21:00 +0100	[thread overview]
Message-ID: <20130910162100.GX13318@ZenIV.linux.org.uk> (raw)

Waiman's conversion of d_path() and bits related to it, kern_path_mountpoint(),
several cleanups and fixes (exportfs one is -stable fodder, IMO).  There
definitely will be more... ;-/  Please, pull from the usual place -
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus

Shortlog:
Al Viro (8):
      afs: get rid of redundant ->d_name.len checks
      exportfs: don't assume that ->iterate() won't feed us too long entries
      prune_super(): sb->s_op is never NULL
      Kill indirect include of file.h from eventfd.h, use fdget() in cgroup.c
      take unlazy_walk() into umount_lookup_last()
      rename user_path_umountat() to user_path_mountpoint_at()
      introduce kern_path_mountpoint()
      split read_seqretry_or_unlock(), convert d_walk() to resulting primitives

Ian Kent (1):
      autofs4 - fix device ioctl mount lookup

Waiman Long (1):
      dcache: Translating dentry into pathname without taking rename_lock

Diffstat:
 fs/afs/dir.c            |   24 -----
 fs/autofs4/dev-ioctl.c  |   23 +++---
 fs/dcache.c             |  220 +++++++++++++++++++++++++++++++----------------
 fs/exportfs/expfs.c     |    2 +-
 fs/internal.h           |    3 +
 fs/namei.c              |  112 +++++++++++++-----------
 fs/namespace.c          |    2 +-
 fs/super.c              |    2 +-
 include/linux/eventfd.h |    3 +-
 include/linux/namei.h   |    4 +-
 kernel/cgroup.c         |   33 ++++----
 11 files changed, 241 insertions(+), 187 deletions(-)

                 reply	other threads:[~2013-09-10 16:21 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=20130910162100.GX13318@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;
as well as URLs for NNTP newsgroup(s).