public inbox for linux-kernel@vger.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,
	linux-usb@vger.kernel.org
Subject: [git pull] gadgetfs fixes
Date: Fri, 13 Mar 2015 16:42:28 +0000	[thread overview]
Message-ID: <20150313164228.GQ29656@ZenIV.linux.org.uk> (raw)

	Assorted fixes around AIO on gadgetfs: leaks, use-after-free,
troubles caused by ->f_op flipping.  Please, pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git gadget

Shortlog:
Al Viro (8):
      new helper: dup_iter()
      move iov_iter.c from mm/ to lib/
      gadget/function/f_fs.c: close leaks
      gadget/function/f_fs.c: use put iov_iter into io_data
      gadget/function/f_fs.c: switch to ->{read,write}_iter()
      gadgetfs: use-after-free in ->aio_read()
      gadget: switch ep_io_operations to ->read_iter/->write_iter
      gadgetfs: get rid of flipping ->f_op in ep_config()

Alan Stern (1):
      gadgetfs: really get rid of switching ->f_op

Diffstat:
 drivers/usb/gadget/function/f_fs.c | 204 +++++++---------
 drivers/usb/gadget/legacy/inode.c  | 466 +++++++++++++++----------------------
 include/linux/uio.h                |   2 +
 lib/Makefile                       |   2 +-
 {mm => lib}/iov_iter.c             |  15 ++
 mm/Makefile                        |   2 +-
 6 files changed, 291 insertions(+), 400 deletions(-)
 rename {mm => lib}/iov_iter.c (97%)

             reply	other threads:[~2015-03-13 16:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 16:42 Al Viro [this message]
2015-03-15  0:39 ` [git pull] gadgetfs fixes Alexander Holler
2015-03-15  1:39   ` Al Viro
2015-03-15  6:35     ` Alexander Holler
2015-03-15  8:17       ` Al Viro
2015-03-15  8:31         ` Alexander Holler
2015-03-16 10:11           ` Alexander Holler
2015-03-15  8:50         ` Alexander Holler
2015-03-15  9:09           ` 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=20150313164228.GQ29656@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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