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 3.19
Date: Wed, 17 Dec 2014 11:02:02 +0100 [thread overview]
Message-ID: <20141217100202.GA19050@tucsk> (raw)
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(-)
next reply other threads:[~2014-12-17 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 10:02 Miklos Szeredi [this message]
2014-12-17 10:15 ` [GIT PULL] fuse update for 3.19 Al Viro
2014-12-17 10:19 ` Miklos Szeredi
2014-12-17 10:23 ` Miklos Szeredi
-- strict thread matches above, loose matches on Subject: below --
2014-12-24 16:53 Marc Dionne
2015-01-05 17:11 ` Miklos Szeredi
2015-01-05 17:33 ` Marc Dionne
2015-01-08 14:11 ` Miklos Szeredi
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=20141217100202.GA19050@tucsk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.