From: Christoph Hellwig <hch@infradead.org>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: block mapping
Date: Thu, 29 Sep 2011 09:55:18 -0400 [thread overview]
Message-ID: <20110929135518.GA3639@infradead.org> (raw)
In-Reply-To: <CALLzPKaWVR5=+S7QtHRpPBkDR5SVsZEAhbUn+G09o1S9JhjFOw@mail.gmail.com>
On Thu, Sep 29, 2011 at 04:35:44PM +0300, Kasatkin, Dmitry wrote:
> Hello All,
>
> I would like to implement such block device, which can store
> additional information along with the block data.
> For example. so if file system has 4k block, I would like to store
> 4k+256b of additional information...
>
> Can such block device be implemented with device mapper?
Given your other recent posts you probably want to take a look at
dm-verity:
http://selinuxproject.org/~jmorris/lss2011_slides/LSS_11_Integrity_checked_block_devices.pdf
(even if that's not strictly what you are asking for here)
next prev parent reply other threads:[~2011-09-29 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 13:35 block mapping Kasatkin, Dmitry
2011-09-29 13:42 ` Zdenek Kabelac
2011-09-29 14:10 ` Kasatkin, Dmitry
2011-09-29 14:19 ` Zdenek Kabelac
2011-09-29 14:27 ` Kasatkin, Dmitry
2011-09-29 13:55 ` Christoph Hellwig [this message]
2011-09-29 14:08 ` Kasatkin, Dmitry
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=20110929135518.GA3639@infradead.org \
--to=hch@infradead.org \
--cc=dm-devel@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 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.