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 fixes
Date: Sun, 3 Mar 2019 03:42:53 +0000	[thread overview]
Message-ID: <20190303034249.GO2217@ZenIV.linux.org.uk> (raw)

	Assorted fixes that sat in -next for a while, all over the
place.

The following changes since commit 1c7fc5cbc33980acd13d668f1c8f0313d6ae9fd8:

  Linux 5.0-rc2 (2019-01-14 10:41:12 +1200)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git fixes

for you to fetch changes up to d3d6a18d7d351cbcc9b33dbedf710e65f8ce1595:

  aio: Fix locking in aio_poll() (2019-02-21 22:16:47 -0500)

----------------------------------------------------------------
Al Viro (2):
      fix cgroup_do_mount() handling of failure exits
      cgroup: saner refcounting for cgroup_root

Bart Van Assche (1):
      aio: Fix locking in aio_poll()

Chandan Rajendra (1):
      copy_mount_string: Limit string length to PATH_MAX

YueHaibing (1):
      exec: Fix mem leak in kernel_read_file

 fs/aio.c                        | 12 ++++++---
 fs/exec.c                       |  2 +-
 fs/kernfs/mount.c               |  8 ++++--
 fs/namespace.c                  |  2 +-
 kernel/cgroup/cgroup-internal.h |  2 +-
 kernel/cgroup/cgroup-v1.c       | 58 +++++++++--------------------------------
 kernel/cgroup/cgroup.c          | 25 +++++++++---------
 7 files changed, 44 insertions(+), 65 deletions(-)

             reply	other threads:[~2019-03-03  3:43 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-03  3:42 Al Viro [this message]
2019-03-03 20:21 ` [git pull] vfs.git fixes Linus Torvalds
2019-03-04 21:30 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2024-02-25  6:59 Al Viro
2024-02-25 17:58 ` pr-tracker-bot
2023-03-10 20:27 Al Viro
2023-03-11  4:52 ` pr-tracker-bot
2021-01-17  3:21 Al Viro
2021-01-17 20:20 ` pr-tracker-bot
2020-10-11 18:06 Al Viro
2020-10-11 18:23 ` pr-tracker-bot
2020-04-28 21:18 Al Viro
2020-04-28 21:45 ` pr-tracker-bot
2020-03-12 22:37 Al Viro
2020-03-12 23:00 ` pr-tracker-bot
2020-02-24  0:22 Al Viro
2020-02-24 20:25 ` pr-tracker-bot
2020-01-26 18:25 Al Viro
2020-01-26 19:30 ` pr-tracker-bot
2019-11-24 20:05 Al Viro
2019-11-25  0:35 ` pr-tracker-bot
2019-11-15  0:50 Al Viro
2019-11-15 17:35 ` pr-tracker-bot
2019-05-05  2:18 Al Viro
2019-05-05 22:10 ` pr-tracker-bot
2018-11-30  5:15 Al Viro
2018-11-30 21:00 ` pr-tracker-bot
2018-08-12 17:44 Al Viro
2018-05-21 18:39 Al Viro
2018-05-21 18:59 ` Linus Torvalds
2018-03-16  1:41 Al Viro
2017-10-22  0:12 Al Viro
2017-10-11  4:54 Al Viro
2017-10-11 17:47 ` Vitaly Mayatskikh
2017-04-27  7:34 Al Viro
2016-07-12  5:16 Al Viro
2016-07-01 20:51 Al Viro
2015-12-06 17:40 Al Viro
2015-11-25 23:08 Al Viro
2015-01-25  2:39 Al Viro
2014-11-22  4:43 Al Viro
2014-11-06  5:04 Al Viro
2013-11-11 16:30 [git pull] vfs.git Al Viro
2013-11-13 13:17 ` [git pull] vfs.git fixes Al Viro

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=20190303034249.GO2217@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).