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-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] more vfs/fs patches
Date: Mon, 20 Jun 2011 18:10:43 +0100	[thread overview]
Message-ID: <20110620171043.GX11521@ZenIV.linux.org.uk> (raw)

Dan's fix for ubifs breakage + removal of a bunch of really dumb
detritus from ->permission() instances + fix for long-standing
stupidity in devcgroups_inode_permission() (the thing is a
no-op for non-devices and that check definitely ought to be
taken to inline wrapper).  Please, pull from the usual place
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git/ #for-linus

Shortlog:

Al Viro (11):
      bad_inode_permission() is safe from RCU mode
      cifs_permission() doesn't need to bail out in RCU mode
      coda_ioctl_permission() is safe in RCU mode
      logfs doesn't need ->permission() at all
      nilfs2_permission() doesn't need to bail out in RCU mode
      proc_fd_permission() is doesn't need to bail out in RCU mode
      reiserfs_permission() doesn't need to bail out in RCU mode
      proc_sys_permission() is OK in RCU mode
      kill obsolete comment for follow_down()
      fix comment in generic_permission()
      devcgroup_inode_permission: take "is it a device node" checks to inlined wrapper

Dan Carpenter (1):
      ubifs: dereferencing an ERR_PTR in ubifs_mount()

Diffstat:

 fs/bad_inode.c                |    3 ---
 fs/cifs/cifsfs.c              |    3 ---
 fs/coda/pioctl.c              |    2 --
 fs/logfs/dir.c                |    8 --------
 fs/namei.c                    |    6 ++----
 fs/nilfs2/inode.c             |    7 +------
 fs/proc/base.c                |    6 +-----
 fs/proc/proc_sysctl.c         |    3 ---
 fs/reiserfs/xattr.c           |    2 --
 fs/ubifs/super.c              |    1 +
 include/linux/device_cgroup.h |   10 +++++++++-
 security/device_cgroup.c      |    8 +-------
 12 files changed, 15 insertions(+), 44 deletions(-)

                 reply	other threads:[~2011-06-20 17:10 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=20110620171043.GX11521@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 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.