linux-kernel - Re: [PATCH v2 2/2] dm unstripe: Add documentation for unstripe target

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20171212145605.GA18169@agk-dp.fab.redhat.com>
Date:   Tue, 12 Dec 2017 14:56:05 +0000
From:   Alasdair G Kergon <agk@...hat.com>
To:     Keith Busch <keith.busch@...el.com>,
        Nikolay Borisov <n.borisov.lkml@...il.com>,
        Scott Bauer <scott.bauer@...el.com>, dm-devel@...hat.com,
        snitzer@...hat.com, agk@...hat.com, linux-kernel@...r.kernel.org,
        jonathan.derrick@...el.com
Subject: Re: [PATCH v2 2/2] dm unstripe: Add documentation for unstripe
        target

On Tue, Dec 12, 2017 at 07:45:56AM -0700, Keith Busch wrote:
> Ah, this device's makers call the "stripe" size what should be called
> "chunk".

If this target is to go anywhere, let's try to define it as 'undoing'
the existing dm-stripe target using primary terminology, field names
etc. as close as possible to our existing target.  We can still mention
any alternative terminology encountered in the documentation.  The
first (simplest) documented example could be a dm-stripe target being
'unstriped'.

Alasdair