From: Omar Sandoval <osandov@osandov.com>
To: linux-btrfs@vger.kernel.org
Cc: kernel-team@fb.com, linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/2] Btrfs: add interface for writing compressed extents directly
Date: Wed, 4 Sep 2019 12:13:24 -0700 [thread overview]
Message-ID: <cover.1567623877.git.osandov@fb.com> (raw)
From: Omar Sandoval <osandov@fb.com>
Hi,
This is an update of my RFC series [1]. Patch 1 is a VFS patch to export
some permission checks. Patch 2 is the actual change.
Changes from the RFC:
- Rebased on misc-next, which now has the cleanups from patches 1-3.
- Generalized the interface to "raw writes" so that we can support,
e.g., encrypted writes in the future.
Note that I kept the compat ioctl implementation the same based on the
discussion in [2].
1: https://lore.kernel.org/linux-btrfs/cover.1565900769.git.osandov@fb.com/
2: https://lore.kernel.org/linux-btrfs/20190903171458.GA7452@vader/
Omar Sandoval (2):
fs: export rw_verify_area()
btrfs: add ioctl for directly writing compressed data
fs/btrfs/compression.c | 6 +-
fs/btrfs/compression.h | 14 +--
fs/btrfs/ctree.h | 6 ++
fs/btrfs/file.c | 13 ++-
fs/btrfs/inode.c | 192 ++++++++++++++++++++++++++++++++++++-
fs/btrfs/ioctl.c | 95 ++++++++++++++++++
fs/internal.h | 5 -
fs/read_write.c | 1 +
include/linux/fs.h | 1 +
include/uapi/linux/btrfs.h | 69 +++++++++++++
10 files changed, 382 insertions(+), 20 deletions(-)
--
2.23.0
next reply other threads:[~2019-09-04 19:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 19:13 Omar Sandoval [this message]
2019-09-04 19:13 ` [PATCH 1/2] fs: export rw_verify_area() Omar Sandoval
2019-09-04 19:13 ` [PATCH 2/2] btrfs: add ioctl for directly writing compressed data Omar Sandoval
2019-09-05 2:10 ` Dave Chinner
2019-09-05 12:16 ` Johannes Thumshirn
2019-09-05 12:51 ` Johannes Thumshirn
2019-09-06 7:46 ` Dave Chinner
2019-09-06 18:19 ` Omar Sandoval
2019-09-06 21:07 ` Dave Chinner
2019-09-06 21:27 ` Omar Sandoval
2019-09-05 10:33 ` Nikolay Borisov
2019-09-19 6:14 ` Omar Sandoval
2019-09-19 7:46 ` Nikolay Borisov
2019-09-19 7:59 ` Omar Sandoval
2019-09-24 10:29 ` Nikolay Borisov
2019-09-10 11:39 ` Filipe Manana
2019-09-19 6:23 ` Omar Sandoval
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=cover.1567623877.git.osandov@fb.com \
--to=osandov@osandov.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).