From: Milan Broz <gmazyland@gmail.com>
To: JeongHyeon Lee <jhs2.lee@samsung.com>,
Mike Snitzer <snitzer@redhat.com>,
Sami Tolvanen <samitolvanen@google.com>
Cc: dm-devel@redhat.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, agk@redhat.com, corbet@lwn.net
Subject: Re: New mode DM-Verity error handling
Date: Tue, 23 Jun 2020 09:28:32 +0200 [thread overview]
Message-ID: <2c3bf8c1-c742-b1e9-6ff6-91b2253638e1@gmail.com> (raw)
In-Reply-To: <250156a6-a2d6-dbfd-daa3-be9c36f0cf36@samsung.com>
On 23/06/2020 01:53, JeongHyeon Lee wrote:
>
> For what reason isn't panic better?
I did not say panic is better, I said that while we have restart already in mainline dm-verity code,
panic() is almost the same, so I see no problem in merging this patch.
Stopping system this way could create more damage if it is not configured properly,
but I think it is quite common to stop the system as fast as possible if data system integrity
is violated...
> If when i suggested new patch, i will send you a patch that increased
> minor version.
I think Mike can fold-in version increase, if the patch is accepted.
But please include these version changes with every new feature.
Actually I am tracking it here for dm-verity as part of veritysetup userspace documentation:
https://gitlab.com/cryptsetup/cryptsetup/-/wikis/DMVerity
Thanks,
Milan
> On 22/06/2020 16:58, Milan Broz wrote:
>> On 18/06/2020 19:09, Mike Snitzer wrote:
>>> On Thu, Jun 18 2020 at 12:50pm -0400,
>>> Sami Tolvanen <samitolvanen@google.com> wrote:
>>>
>>>> On Thu, Jun 18, 2020 at 11:44:45AM -0400, Mike Snitzer wrote:
>>>>> 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.
>>>> That's exactly how the restart mode works on some Android devices. The
>>>> bootloader sees the verification error and puts the device in recovery
>>>> mode. Using the restart mode on systems without firmware support won't
>>>> make sense, obviously.
>>> OK, so I need further justification from Samsung why they are asking for
>>> this panic mode.
>> I think when we have reboot already, panic is not much better :-)
>>
>> Just please note that dm-verity is used not only in Android world (with own tooling)
>> but in normal Linux distributions, and I need to modify userspace (veritysetup) to support
>> and recognize this flag.
>>
>> Please *always* increase minor dm-verity target version when adding a new feature
>> - we can then provide some better hint if it is not supported.
>>
>> Thanks,
>> Milan
>>
>>
next prev parent reply other threads:[~2020-06-23 7:28 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] " JeongHyeon Lee
2020-06-18 15:44 ` Mike Snitzer
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 [this message]
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=2c3bf8c1-c742-b1e9-6ff6-91b2253638e1@gmail.com \
--to=gmazyland@gmail.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 \
--cc=samitolvanen@google.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
all inboxes | Powered by JetHome®