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] more autofs bits
Date: Tue, 18 Jan 2011 06:50:28 +0000	[thread overview]
Message-ID: <20110118065028.GL22723@ZenIV.linux.org.uk> (raw)

	Contains: fix for leak in do_loopback(), a couple of autofs
fixes from Ian and a bunch of autofs cleanups (some from a year ago ;-/)
I'd finally got around to.  Again, this is not all - there'll be one
more later tonight.  This one is just autofs bits.  Please, pull from

git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git/ for-linus

Shortlog:
Al Viro (8):
      autofs4: keep symlink body in inode->i_private
      autofs4: autofs4_mkroot() is not different from autofs4_init_ino()
      autofs4: pass mode to autofs4_get_inode() explicitly
      autofs4: kill ->size in autofs_info
      autofs4: autofs4_get_inode() doesn't need autofs_info * argument anymore
      autofs4: mkdir and symlink always get a dentry that had passed lookup
      autofs4: split autofs4_init_ino()
      autofs4: clean ->d_release() and autofs4_free_ino() up

Ian Kent (3):
      autofs4 - fix get_next_positive_dentry()
      vfs - fix dentry ref count in do_lookup()
      autofs4 - fix debug print in autofs4_lookup()

Diffstat:
 fs/autofs4/autofs_i.h |   14 ++------
 fs/autofs4/expire.c   |    4 +-
 fs/autofs4/inode.c    |   88 ++++++++++++------------------------------------
 fs/autofs4/root.c     |   74 +++++++++++++++++++---------------------
 fs/autofs4/symlink.c  |    3 +-
 fs/namei.c            |    4 ++-
 6 files changed, 66 insertions(+), 121 deletions(-)

                 reply	other threads:[~2011-01-18  6:50 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=20110118065028.GL22723@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).