From: Mikulas Patocka <mpatocka@redhat.com>
To: Mike Snitzer <msnitzer@redhat.com>, Milan Broz <mbroz@redhat.com>
Cc: dm-devel@redhat.com
Subject: [PATCH 0/9] dm-integrity patches
Date: Wed, 06 Jun 2018 17:33:07 +0200 [thread overview]
Message-ID: <20180606153307.423442513@debian.vm> (raw)
Hi
Here I'm sending the dm-integrity patches. It would be nice if you could
send them in this merge window.
The major changes are:
* avoid starvation in range locking
* use external metadata device
* recalculate integrity tags automatically
Mikulas
next reply other threads:[~2018-06-06 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 15:33 Mikulas Patocka [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-03 18:13 [PATCH 0/9] dm-integrity patches Mikulas Patocka
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=20180606153307.423442513@debian.vm \
--to=mpatocka@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mbroz@redhat.com \
--cc=msnitzer@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.