linux-kernel - [GIT PULL] fuse update for 3.15

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: <20140403135141.GD10187@tucsk.piliscsaba.szeredi.hu>
Date:	Thu, 3 Apr 2014 15:51:41 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: [GIT PULL] fuse update for 3.15

Hi Linus,

Please pull the following:

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

This series adds cached writeback support to fuse, improving write throughput.

Thanks,
Miklos
----

Maxim Patlasov (3):
      fuse: Trust kernel i_mtime only
      fuse: restructure fuse_readpage()
      fuse: fuse_flush() should wait on writeback

Pavel Emelyanov (8):
      fuse: Linking file to inode helper
      fuse: Prepare to handle short reads
      fuse: Connection bit for enabling writeback
      fuse: Trust kernel i_size only
      fuse: Flush files on wb close
      fuse: Implement write_begin/write_end callbacks
      fuse: Fix O_DIRECT operations vs cached writeback misorder
      fuse: Turn writeback cache on

Rajat Jain (1):
      fuse: fix "uninitialized variable" warning

---
 fs/fuse/cuse.c            |   5 +-
 fs/fuse/dir.c             | 119 ++++++++++++++++---
 fs/fuse/file.c            | 286 +++++++++++++++++++++++++++++++++++++---------
 fs/fuse/fuse_i.h          |  22 +++-
 fs/fuse/inode.c           |  29 ++++-
 include/uapi/linux/fuse.h |   7 +-
 6 files changed, 384 insertions(+), 84 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/