From: "Colin Walters" <walters@verbum.org>
To: "Chris Mason" <clm@fb.com>
Cc: "Dave Chinner" <david@fromorbit.com>,
"Jann Horn" <jannh@google.com>,
"Omar Sandoval" <osandov@osandov.com>,
"Aleksa Sarai" <cyphar@cyphar.com>,
"Jens Axboe" <axboe@kernel.dk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"Linux API" <linux-api@vger.kernel.org>,
"Kernel Team" <Kernel-team@fb.com>,
"Andy Lutomirski" <luto@kernel.org>
Subject: Re: [RFC PATCH 2/3] add RWF_ENCODED for writing compressed data
Date: Thu, 26 Sep 2019 08:17:12 -0400 [thread overview]
Message-ID: <4e6e03c1-b2f4-4841-99af-cbb75f33c14d@www.fastmail.com> (raw)
In-Reply-To: <FF3F534F-B40D-4D7D-956B-F1B63C4751CC@fb.com>
On Wed, Sep 25, 2019, at 10:56 AM, Chris Mason wrote:
> The data is verified while being decompressed, but that's a fairly large
> fuzzing surface (all of zstd, zlib, and lzo). A lot of people will
> correctly argue that we already have that fuzzing surface today, but I'd
> rather not make a really easy way to stuff arbitrary bytes through the
> kernel decompression code until all the projects involved sign off.
Right. So maybe have this start of as a BTRFS ioctl and require
privileges? I assume that's sufficient for what Omar wants.
(Are there actually any other popular Linux filesystems that do transparent compression anyways?)
next prev parent reply other threads:[~2019-09-26 12:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 6:53 [RFC PATCH 0/3] fs: interface for directly writing encoded (e.g., compressed) data Omar Sandoval
2019-09-19 6:53 ` [RFC PATCH 1/3] fs: pass READ/WRITE to kiocb_set_rw_flags() Omar Sandoval
2019-09-20 14:38 ` Jan Kara
2019-09-19 6:53 ` [PATCH] readv.2: Document new RWF_ENCODED flag to pwritev2() Omar Sandoval
2019-09-19 6:53 ` [RFC PATCH 2/3] fs: add RWF_ENCODED for writing compressed data Omar Sandoval
2019-09-19 15:44 ` Jann Horn
2019-09-20 16:25 ` Jens Axboe
2019-09-24 17:15 ` Omar Sandoval
2019-09-24 19:35 ` Omar Sandoval
2019-09-24 20:01 ` Jann Horn
2019-09-24 20:22 ` Christian Brauner
2019-09-24 20:50 ` Matthew Wilcox
2019-09-24 20:38 ` Omar Sandoval
2019-09-25 7:11 ` Dave Chinner
2019-09-25 12:07 ` Colin Walters
2019-09-25 14:56 ` [RFC PATCH 2/3] " Chris Mason
2019-09-26 12:17 ` Colin Walters [this message]
2019-09-26 17:46 ` Omar Sandoval
2019-09-25 15:08 ` [RFC PATCH 2/3] fs: " Theodore Y. Ts'o
2019-09-25 22:52 ` Dave Chinner
2019-09-26 0:36 ` Omar Sandoval
2019-09-19 6:53 ` [RFC PATCH 3/3] btrfs: implement encoded (compressed) writes 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=4e6e03c1-b2f4-4841-99af-cbb75f33c14d@www.fastmail.com \
--to=walters@verbum.org \
--cc=Kernel-team@fb.com \
--cc=axboe@kernel.dk \
--cc=clm@fb.com \
--cc=cyphar@cyphar.com \
--cc=david@fromorbit.com \
--cc=jannh@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=osandov@osandov.com \
/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.