mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] fuse update for 4.20
Date: Wed, 31 Oct 2018 21:31:42 +0100	[thread overview]
Message-ID: <20181031203142.GG23439@veci.piliscsaba.redhat.com> (raw)

Hi Linus,

Please pull from:

  git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git tags/fuse-update-4.20

As well as the usual bug fixes, this adds the following new features:

 - cached readdir and readlink
 - max I/O size increased from 128k to 1M
 - improved performance and scalability of request queues
 - copy_file_range support

The only non-fuse bits are trivial cleanups of macros in <linux/bitops.h>.

Thanks,
Miklos

----------------------------------------------------------------
Constantine Shulyupin (1):
      fuse: add max_pages to init_out

Dan Schatzberg (1):
      fuse: enable caching of symlinks

Kirill Tkhai (10):
      fuse: Fix use-after-free in fuse_dev_do_read()
      fuse: Fix use-after-free in fuse_dev_do_write()
      fuse: use list_first_entry() in flush_bg_queue()
      fuse: use READ_ONCE on congestion_threshold and max_background
      fuse: add locking to max_background and congestion_threshold changes
      fuse: introduce fc->bg_lock
      fuse: do not take fc->lock in fuse_request_send_background()
      fuse: change interrupt requests allocation algorithm
      fuse: kill req->intr_unique
      fuse: Use hash table to link processing request

Miklos Szeredi (18):
      fuse: set FR_SENT while locked
      fuse: fix blocked_waitq wakeup
      fuse: split out readdir.c
      fuse: add FOPEN_CACHE_DIR
      fuse: extract fuse_emit() helper
      fuse: allow caching readdir
      fuse: allow using readdir cache
      fuse: add readdir cache version
      fuse: use mtime for readdir cache verification
      fuse: use iversion for readdir cache verification
      fuse: reduce size of struct fuse_inode
      fuse: allocate page array more efficiently
      fuse: realloc page array
      bitops: protect variables in set_mask_bits() macro
      bitops: protect variables in bit_clear_unless() macro
      fuse: allow fine grained attr cache invaldation
      fuse: don't need GETATTR after every READ
      fuse: only invalidate atime in direct read

Niels de Vos (1):
      fuse: add support for copy_file_range()

---
 fs/fuse/Makefile          |   2 +-
 fs/fuse/control.c         |  34 ++-
 fs/fuse/dev.c             | 221 +++++++++++-------
 fs/fuse/dir.c             | 381 +++++++++----------------------
 fs/fuse/file.c            | 158 ++++++++++---
 fs/fuse/fuse_i.h          | 124 ++++++++--
 fs/fuse/inode.c           |  53 +++--
 fs/fuse/readdir.c         | 569 ++++++++++++++++++++++++++++++++++++++++++++++
 include/linux/bitops.h    |  30 +--
 include/uapi/linux/fuse.h | 119 ++++++----
 10 files changed, 1201 insertions(+), 490 deletions(-)
 create mode 100644 fs/fuse/readdir.c

             reply	other threads:[~2018-10-31 20:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 20:31 Miklos Szeredi [this message]
2018-10-31 21:52 ` Linus Torvalds

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=20181031203142.GG23439@veci.piliscsaba.redhat.com \
    --to=miklos@szeredi.hu \
    --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

all inboxes | Powered by JetHome®