From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: Exactly what is wrong with RAID5/6
Date: Wed, 21 Jun 2017 14:43:21 +0200 [thread overview]
Message-ID: <1498049001.6359.4.camel@scientia.net> (raw)
In-Reply-To: <60421001-5d74-2fb4-d916-7a397f246f20@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 421 bytes --]
On Wed, 2017-06-21 at 16:45 +0800, Qu Wenruo wrote:
> Btrfs is always using device ID to build up its device mapping.
> And for any multi-device implementation (LVM,mdadam) it's never a
> good
> idea to use device path.
Isn't it rather the other way round? Using the ID is bad? Don't you
remember our discussion about using leaked UUIDs (or accidental
collisions) for all kinds of attacks?
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]
next prev parent reply other threads:[~2017-06-21 12:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 22:57 Exactly what is wrong with RAID5/6 waxhead
2017-06-20 23:25 ` Hugo Mills
2017-06-21 3:48 ` Chris Murphy
2017-06-21 6:51 ` Marat Khalili
2017-06-21 7:31 ` Peter Grandi
2017-06-21 17:13 ` Andrei Borzenkov
2017-06-21 18:43 ` Chris Murphy
2017-06-21 8:45 ` Qu Wenruo
2017-06-21 12:43 ` Christoph Anton Mitterer [this message]
2017-06-21 13:41 ` Austin S. Hemmelgarn
2017-06-21 17:20 ` Andrei Borzenkov
2017-06-21 17:30 ` Austin S. Hemmelgarn
2017-06-21 17:03 ` Goffredo Baroncelli
2017-06-22 2:05 ` Qu Wenruo
2017-06-21 18:24 ` Chris Murphy
2017-06-21 20:12 ` Goffredo Baroncelli
2017-06-21 23:19 ` Chris Murphy
2017-06-22 2:12 ` Qu Wenruo
2017-06-22 2:43 ` Chris Murphy
2017-06-22 3:55 ` Qu Wenruo
2017-06-22 5:15 ` Goffredo Baroncelli
2017-06-23 17:25 ` Michał Sokołowski
2017-06-23 18:45 ` Austin S. Hemmelgarn
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=1498049001.6359.4.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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 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).