Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Mikulas Patocka <mpatocka@redhat.com>,
	Mike Snitzer <snitzer@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-raid@vger.kernel.org
Subject: Re: DM_INTEGRITY Kconfig help (was: Re: dm: add integrity target)
Date: Thu, 4 May 2017 09:31:00 +0200	[thread overview]
Message-ID: <6988fc7b-1ab4-4c7a-c7c9-121271ddd970@gmail.com> (raw)
In-Reply-To: <CAMuHMdWafrUq0tbHsOS2Gm579Amv0LpYAqk=Kqg4t8fqgbWDgw@mail.gmail.com>

On 05/04/2017 08:03 AM, Geert Uytterhoeven wrote:
>> +config DM_INTEGRITY
>> +       tristate "Integrity target"
>> +       depends on BLK_DEV_DM
>> +       select BLK_DEV_INTEGRITY
>> +       select DM_BUFIO
>> +       select CRYPTO
>> +       select ASYNC_XOR
>> +       ---help---
>> +          This is the integrity target.
> 
> Which is...?
> 
> Can you please extend the help message for the uneducated?

Yes, sorry, this is our oversight.

Mike already promised that this text will be extended in the next patchset.

For now you can find the description in documentation
Documentation/device-mapper/dm-integrity.txt

"The dm-integrity target emulates a block device that has additional
per-sector tags that can be used for storing integrity information."

(The major designed use case is for providing metadata space for tags
for authenticated encryption in dm-crypt but it can be used also as
a standalone target.)

Thanks,
Milan

  reply	other threads:[~2017-05-04  7:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04  6:03 DM_INTEGRITY Kconfig help (was: Re: dm: add integrity target) Geert Uytterhoeven
2017-05-04  7:31 ` Milan Broz [this message]
2017-05-04  7:39   ` Geert Uytterhoeven

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=6988fc7b-1ab4-4c7a-c7c9-121271ddd970@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=snitzer@redhat.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