From: Diego Calleja <diegocg@gmail.com>
To: linux-btrfs@vger.kernel.org, Andrei Bacs <andrei.bacs@gmail.com>
Cc: cpu808694@gmail.com, Cristiano Giuffrida <c.giuffrida@vu.nl>,
"Bos, H.J." <h.j.bos@vu.nl>, Kaveh Razavi <kaveh@ethz.ch>,
"Bacs, A." <a.bacs@vu.nl>
Subject: Re: inline deduplication security issues
Date: Sun, 23 Jan 2022 20:18:44 +0100 [thread overview]
Message-ID: <1828959.tdWV9SEqCh@arch> (raw)
In-Reply-To: <CAKDzk=-HZardsLFH5c9HYre73NYNszUJqpfsh0YJnnaQToB3BA@mail.gmail.com>
El sábado, 22 de enero de 2022 19:42:47 (CET) Andrei Bacs escribió:
> We have found security issues with inline deduplication in storage
> systems, using ZFS and Btrfs and running examples. See the attached
> paper for details.
(Not actually a btrfs developer here)
I am confused, Btrfs does not support inline deduplication. The inline
deduplication implementation used in that paper is pretty old and as far as I
know it's not maintained (people seem to be happy with out of band
deduplication).
You might want to contact the developer on the inline implementation: https://
lore.kernel.org/linux-btrfs/20181106064122.6154-1-lufq.fnst@cn.fujitsu.com/
Also, this is a public mailing list, so there is no point in waiting until
23rd of February 2022 to make things public.
Kind regards.
next prev parent reply other threads:[~2022-01-23 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 18:42 inline deduplication security issues Andrei Bacs
2022-01-23 19:18 ` Diego Calleja [this message]
2022-01-24 1:38 ` Su Yue
2022-01-24 11:45 ` Qu Wenruo
2022-01-24 16:17 ` David Sterba
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=1828959.tdWV9SEqCh@arch \
--to=diegocg@gmail.com \
--cc=a.bacs@vu.nl \
--cc=andrei.bacs@gmail.com \
--cc=c.giuffrida@vu.nl \
--cc=cpu808694@gmail.com \
--cc=h.j.bos@vu.nl \
--cc=kaveh@ethz.ch \
--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.