From: David Sterba <dsterba@suse.cz>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: zerofree btrfs support?
Date: Wed, 14 Mar 2018 20:38:47 +0100 [thread overview]
Message-ID: <20180314193847.GR32007@twin.jikos.cz> (raw)
In-Reply-To: <1520650525.5641.47.camel@scientia.net>
On Sat, Mar 10, 2018 at 03:55:25AM +0100, Christoph Anton Mitterer wrote:
> Hi.
>
> Just wondered... was it ever planned (or is there some equivalent) to
> get support for btrfs in zerofree?
The zerofree was requested, eg. here
https://bugzilla.kernel.org/show_bug.cgi?id=69121
and there was a discussion under proposed patches on fsdevel 3 years
ago, message-id is 1422896713-25367-1-git-send-email-holler@ahsoftware.de
tl;dr there's nothing like zeofree now, because.
Because the security reasons are not considered good enough and giving
false sense of security. Clearing the qemu images sounds good but
there's another way to do that via trim.
I have a prototype code for that and after the years, seeing the request
again, I'm not against adding it as long as it's not advertised as a
security feature.
The zeroing simply builds on top of the trim code, so it's merely adding
the ioctl interface and passing down the desired operation.
next prev parent reply other threads:[~2018-03-14 19:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-10 2:55 zerofree btrfs support? Christoph Anton Mitterer
2018-03-10 8:16 ` Adam Borowski
2018-03-10 14:19 ` Christoph Anton Mitterer
2018-03-10 14:37 ` Roman Mamedov
2018-03-10 15:50 ` Adam Borowski
2018-03-10 16:58 ` Christoph Anton Mitterer
2018-03-10 18:31 ` Roman Mamedov
2018-03-10 18:39 ` Christoph Anton Mitterer
2018-03-10 16:55 ` Christoph Anton Mitterer
2018-03-14 19:38 ` David Sterba [this message]
2018-03-15 2:54 ` Christoph Anton Mitterer
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=20180314193847.GR32007@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=calestyo@scientia.net \
--cc=linux-btrfs@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 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.