mirror of https://lore.kernel.org/lkml/
 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,
	linux-security-module@vger.kernel.org
Subject: [git pull] vfs.git#work.const-path
Date: Tue, 17 May 2016 22:31:25 +0100	[thread overview]
Message-ID: <20160517213125.GK14480@ZenIV.linux.org.uk> (raw)

struct path is passed by reference to a bunch of Linux S&M methods; in
theory, there's nothing to stop them from modifying the damn thing and
LSM community being what it is, sooner or later some enterprising soul
is going to decide that it's a good idea.  Let's remove the temptation
and constify all of those...

The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:

  Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.const-path

for you to fetch changes up to 81cd8896a64cc34bd59f097fa619b11ab40ca7a6:

  constify ima_d_path() (2016-03-28 00:47:52 -0400)

----------------------------------------------------------------
Al Viro (18):
      [apparmor] constify struct path * in a bunch of helpers
      constify security_path_truncate()
      constify vfs_truncate()
      apparmor_path_truncate(): path->mnt is never NULL
      tomoyo: constify assorted struct path *
      constify chown_common/security_path_chown
      constify security_sb_mount()
      constify chmod_common/security_path_chmod
      apparmor: new helper - common_path_perm()
      apparmor: constify aa_path_link()
      apparmor: constify common_perm_...()
      constify security_path_{unlink,rmdir}
      constify security_path_{mkdir,mknod,symlink}
      apparmor: remove useless checks for NULL ->mnt
      constify security_path_{link,rename}
      constify security_path_chroot()
      constify security_sb_pivotroot()
      constify ima_d_path()

 fs/namei.c                       |  2 +-
 fs/open.c                        |  6 +--
 include/linux/fs.h               |  2 +-
 include/linux/lsm_hooks.h        | 28 +++++++-------
 include/linux/security.h         | 58 ++++++++++++++--------------
 net/unix/af_unix.c               |  2 +-
 security/apparmor/file.c         |  4 +-
 security/apparmor/include/file.h |  4 +-
 security/apparmor/include/path.h |  2 +-
 security/apparmor/lsm.c          | 83 +++++++++++++++-------------------------
 security/apparmor/path.c         |  8 ++--
 security/integrity/ima/ima.h     |  2 +-
 security/integrity/ima/ima_api.c |  2 +-
 security/security.c              | 28 +++++++-------
 security/selinux/hooks.c         |  2 +-
 security/tomoyo/common.h         | 12 +++---
 security/tomoyo/file.c           | 10 ++---
 security/tomoyo/mount.c          |  4 +-
 security/tomoyo/tomoyo.c         | 28 +++++++-------
 19 files changed, 132 insertions(+), 155 deletions(-)

                 reply	other threads:[~2016-05-17 21:31 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=20160517213125.GK14480@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@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

all inboxes | Powered by JetHome®