All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] VFS fixes for 3.16
Date: Sat, 26 Jul 2014 08:02:18 -0700	[thread overview]
Message-ID: <20140726150218.GA8770@infradead.org> (raw)
In-Reply-To: <20140724153057.GA1584@infradead.org>

Hi Linus,

here's a userspace triggered vfsmount leak fix, and a compile warning
fix for 3.16:


The following changes since commit 82e13c71bc655b6dc7110da4e164079dadb44892:

  Merge branch 'for-3.16' of git://linux-nfs.org/~bfields/linux (2014-07-23 17:55:11 -0700)

are available in the git repository at:


  git://git.infradead.org/users/hch/vfs.git vfs-for-3.16

for you to fetch changes up to 295dc39d941dc2ae53d5c170365af4c9d5c16212:

  fs: umount on symlink leaks mnt count (2014-07-24 06:18:12 -0400)

----------------------------------------------------------------
Boaz Harrosh (1):
      direct-io: fix uninitialized warning in do_direct_IO()

Vasily Averin (1):
      fs: umount on symlink leaks mnt count

 fs/direct-io.c | 14 +++++++-------
 fs/namei.c     |  3 ++-
 2 files changed, 9 insertions(+), 8 deletions(-)

  parent reply	other threads:[~2014-07-26 15:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16 11:41 VFS tree for 3.17? Christoph Hellwig
2014-07-22 16:24 ` Christoph Hellwig
2014-07-22 16:47   ` Richard Weinberger
2014-07-24 15:30   ` Christoph Hellwig
2014-07-24 16:35     ` Miklos Szeredi
2014-07-26 15:03       ` Christoph Hellwig
2014-07-24 23:18     ` Stephen Rothwell
2014-07-26 15:02     ` Christoph Hellwig [this message]
2014-07-30 17:20     ` J. Bruce Fields
2014-07-30 20:54       ` Christoph Hellwig

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=20140726150218.GA8770@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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.