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 assorted fixes
Date: Sun, 22 Jul 2018 17:39:09 +0100	[thread overview]
Message-ID: <20180722163909.GG30522@ZenIV.linux.org.uk> (raw)

	Fix several places that screw up cleanups after failures halfway
through opening a file (one open-coding filp_clone_open() and getting
it wrong, two misusing alloc_file()).  That part is -stable fodder from
#work.open.
	And Christoph's regression fix for uapi breakage in aio series;
include/uapi/linux/aio_abi.h shouldn't be pulling in the kernel definition
of sigset_t, the reason for doing so in the first place had been bogus - 
there's no need to expose struct __aio_sigset in aio_abi.h at all.

The following changes since commit 877f919e192a09e77962a13d7165783027dee5fd:

  proc: add proc_seq_release (2018-06-27 20:44:38 -0400)

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 9ba546c01976a426292af99e682a557075d6c010:

  aio: don't expose __aio_sigset in uapi (2018-07-17 23:26:58 -0400)

----------------------------------------------------------------
Al Viro (3):
      drm_mode_create_lease_ioctl(): fix open-coded filp_clone_open()
      cxl_getfile(): fix double-iput() on alloc_file() failures
      ocxlflash_getfile(): fix double-iput() on alloc_file() failures

Christoph Hellwig (1):
      aio: don't expose __aio_sigset in uapi

 drivers/gpu/drm/drm_lease.c     | 16 +---------------
 drivers/misc/cxl/api.c          |  8 ++++----
 drivers/scsi/cxlflash/ocxl_hw.c |  5 ++---
 fs/aio.c                        |  5 +++++
 fs/internal.h                   |  1 -
 include/linux/fs.h              |  1 +
 include/linux/syscalls.h        |  1 +
 include/uapi/linux/aio_abi.h    |  6 ------
 8 files changed, 14 insertions(+), 29 deletions(-)

             reply	other threads:[~2018-07-22 17:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-22 16:39 Al Viro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-12-22 23:23 [git pull] vfs.git assorted fixes Al Viro
2019-12-23  1:05 ` 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=20180722163909.GG30522@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).