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

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>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 17 Dec 2014 11:02:02 +0100
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.19

Hi Linus,

Please pull from:

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

First part makes sure we don't hold up umount with pending async requests.  In
addition to being a cleanup, this is a small behavioral change (for the better)
and unlikely to break anything.  Second part prepares for a cleanup of the fuse
device I/O code by adding a helper for simple request submission, with some
savings in line numbers already realized.

Thanks,
Miklos

---
Miklos Szeredi (6):
      fuse: don't wake up reserved req in fuse_conn_kill()
      fuse: flush requests on umount
      fuse: hold inode instead of path after release
      fuse: reduce max out args
      fuse: introduce fuse_simple_request() helper
      fuse: use file_inode() in fuse_file_fallocate()

---
 fs/fuse/cuse.c   |   2 +-
 fs/fuse/dev.c    |  29 +++
 fs/fuse/dir.c    | 538 ++++++++++++++++++++++---------------------------------
 fs/fuse/file.c   | 230 ++++++++----------------
 fs/fuse/fuse_i.h |  45 +++--
 fs/fuse/inode.c  |  39 +---
 6 files changed, 359 insertions(+), 524 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/