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.git#work.misc
Date: Wed, 18 May 2016 19:40:16 +0100	[thread overview]
Message-ID: <20160518184016.GS14480@ZenIV.linux.org.uk> (raw)

	Assorted cleanups and fixes all over the place.

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.misc

for you to fetch changes up to 2c4cb04300fa160e9d78335c74184c4e66a56437:

  coredump: only charge written data against RLIMIT_CORE (2016-05-12 16:55:50 -0400)

----------------------------------------------------------------
Al Viro (6):
      mtd: switch open_mtd_by_chdev() to use of vfs_stat()
      mtd: switch ubi_open_volume_path() to vfs_stat()
      __d_alloc(): treat NULL name as QSTR("/", 1)
      bpf: reject invalid names right in ->lookup()
      ecryptfs: avoid multiple aliases for directories
      ecryptfs_lookup(): try either only encrypted or plaintext name

Omar Sandoval (2):
      coredump: get rid of coredump_params->written
      coredump: only charge written data against RLIMIT_CORE

 arch/powerpc/platforms/cell/spufs/coredump.c |  5 +-
 drivers/mtd/ubi/build.c                      | 13 ++---
 drivers/mtd/ubi/kapi.c                       | 19 +++----
 fs/binfmt_elf.c                              |  2 +-
 fs/binfmt_elf_fdpic.c                        |  2 +-
 fs/coredump.c                                |  5 +-
 fs/dcache.c                                  | 13 +++--
 fs/ecryptfs/inode.c                          | 85 ++++++++++++----------------
 kernel/bpf/inode.c                           | 37 +++---------
 9 files changed, 69 insertions(+), 112 deletions(-)

             reply	other threads:[~2016-05-18 18:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18 18:40 Al Viro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-17  3:04 [git pull] vfs.git work.misc Al Viro
2019-03-11  0:39 [git pull] vfs.git #work.misc Al Viro
2019-03-12 22:20 ` pr-tracker-bot
2022-08-14  0:23 Al Viro
2022-08-14  0:39 ` Linus Torvalds
2022-08-14  0:39 ` pr-tracker-bot

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=20160518184016.GS14480@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).