From: Vivek Goyal <vgoyal@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: wad@chromium.org, msb@chromium.org, mpatocka@redhat.com
Subject: Re: [PATCH] dm-verity: Add error handling modes for corrupted blocks
Date: Tue, 17 Mar 2015 11:27:49 -0400 [thread overview]
Message-ID: <20150317152749.GA24901@redhat.com> (raw)
In-Reply-To: <20150316155559.GA32397@google.com>
On Mon, Mar 16, 2015 at 03:55:59PM +0000, Sami Tolvanen wrote:
> Add device specific modes to dm-verity to specify how corrupted
> blocks should be handled. The following modes are defined:
>
> - DM_VERITY_MODE_EIO is the default behavior, where reading a
> corrupted block results in -EIO.
>
> - DM_VERITY_MODE_LOGGING only logs corrupted blocks, but does
> not block the read.
>
> - DM_VERITY_MODE_RESTART calls kernel_restart when a corrupted
> block is discovered.
What's the idea behind kernel restart mode ? If a corrupted block is in
the path of boot, will we not get into a continuous reboot cycle.
Thanks
Vivek
next prev parent reply other threads:[~2015-03-17 15:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 15:55 [PATCH] dm-verity: Add error handling modes for corrupted blocks Sami Tolvanen
2015-03-16 22:13 ` Will Drewry
2015-03-17 0:45 ` Alasdair G Kergon
2015-03-17 10:35 ` Sami Tolvanen
2015-03-17 10:23 ` Sami Tolvanen
2015-03-17 0:37 ` Alasdair G Kergon
2015-03-17 10:36 ` Sami Tolvanen
2015-03-17 15:27 ` Vivek Goyal [this message]
2015-03-17 16:06 ` Sami Tolvanen
2015-03-17 18:03 ` Vivek Goyal
2015-03-18 13:24 ` Sami Tolvanen
2015-03-18 15:42 ` Mikulas Patocka
2015-03-18 15:49 ` Sami Tolvanen
2015-03-17 16:37 ` [PATCHv2] " Sami Tolvanen
2015-03-17 18:50 ` Alasdair G Kergon
2015-03-18 13:26 ` Sami Tolvanen
2015-03-18 15:52 ` [PATCHv3] " Sami Tolvanen
2015-03-19 22:18 ` Mike Snitzer
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=20150317152749.GA24901@redhat.com \
--to=vgoyal@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mpatocka@redhat.com \
--cc=msb@chromium.org \
--cc=wad@chromium.org \
/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