linux-kernel - [git pull] fuse: support splice() on fuse device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <E1OHac4-0000AH-ED@pomaz-ex.szeredi.hu>
Date:	Thu, 27 May 2010 12:46:56 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	torvalds@...ux-foundation.org
CC:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: [git pull] fuse: support splice() on fuse device

Linus,

This series adds support for splice() on the fuse device, allowing
userspace filesystem implementations to transfer data to/from the
kernel with reduced number of memory copies.

The only changes outside the fuse tree are addition of EXPORT_SYMBOLs.

Please pull from:

  git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-linus

Thanks,
Miklos
---

Dan Carpenter (1):
      fuse: remove unneeded variable

Miklos Szeredi (8):
      fuse: use get_user_pages_fast()
      fuse: get page reference for readpages
      fuse: support splice() writing to fuse device
      mm: export lru_cache_add_*() to modules
      mm: export remove_from_page_cache() to modules
      fuse: allow splice to move pages
      fuse: support splice() reading from fuse device
      mm: export generic_pipe_buf_*() to modules

---
 fs/fuse/dev.c        |  527 +++++++++++++++++++++++++++++++++++++++++++-------
 fs/fuse/file.c       |   39 +++--
 fs/fuse/fuse_i.h     |    3 +
 fs/pipe.c            |    6 +
 include/linux/fuse.h |    5 +-
 mm/filemap.c         |    1 +
 mm/swap.c            |    1 +
 7 files changed, 500 insertions(+), 82 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/