From: Mike Snitzer <snitzer@redhat.com>
To: JeongHyeon Lee <jhs2.lee@samsung.com>
Cc: agk@redhat.com, dm-devel@redhat.com, corbet@lwn.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: New mode DM-Verity error handling
Date: Thu, 18 Jun 2020 11:44:45 -0400 [thread overview]
Message-ID: <20200618154444.GB18007@redhat.com> (raw)
In-Reply-To: <98eac3fc-c399-625d-5730-29853b3a0771@samsung.com>
On Thu, Jun 18 2020 at 2:56am -0400,
JeongHyeon Lee <jhs2.lee@samsung.com> wrote:
> Hello, Dear devcice-mapper maintainers.
>
> I'm JeongHyeon Lee, work in Samsung. I'm chage of DM-Verity feature with
> Mr. sunwook eom.
> I have a patch or suggestion about DM-Verity error handling.
>
> Our device (smart phone) need DM-Verity feature. So I hope there is new
> mode DM-Verity error handling.
> This new mode concept is When detect corrupted block, will be go to panic.
>
> Because our team policy is found device DM-Verity error, device will go
> panic.
> And then analyze what kind of device fault (crash UFS, IO error, DRAM
> bit flip etc)
>
> In addition to the smart phone, I would like to have an option that
> users or administrators can use accordingly.
> There are patch contents in the attachment. I would really appreciate it
> if you could check it.
>
> I will look forward to hearing from yours.
> Thank you :)
>
I do not accept that panicing the system because of verity failure is
reasonable.
In fact, even rebooting (via DM_VERITY_MODE_RESTART) looks very wrong.
The device should be put in a failed state and left for admin recovery.
Mike
next prev parent reply other threads:[~2020-06-18 15:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200618070250epcas1p409eb2ddd19ecc5d55c219ac3dc884f25@epcas1p4.samsung.com>
2020-06-18 6:56 ` [patch] New mode DM-Verity error handling JeongHyeon Lee
2020-06-18 15:44 ` Mike Snitzer [this message]
2020-06-18 16:50 ` [dm-devel] " Sami Tolvanen
2020-06-18 17:09 ` Mike Snitzer
2020-06-22 0:27 ` JeongHyeon Lee
2020-06-22 7:58 ` Milan Broz
2020-06-22 23:53 ` JeongHyeon Lee
2020-06-23 7:28 ` Milan Broz
2020-06-23 8:08 ` JeongHyeon Lee
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=20200618154444.GB18007@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=corbet@lwn.net \
--cc=dm-devel@redhat.com \
--cc=jhs2.lee@samsung.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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.