From: Sami Tolvanen <samitolvanen@google.com>
To: Milan Broz <gmazyland@gmail.com>
Cc: Bongkyu Kim <bongkyu.kim@lge.com>,
agk@redhat.com, snitzer@redhat.com, dm-devel@redhat.com,
shli@kernel.org, linux-raid@vger.kernel.org,
linux-kernel@vger.kernel.org, Will Drewry <wad@chromium.org>
Subject: Re: [PATCH] dm verity: deferred hash checking for restart/logging mode
Date: Mon, 24 Apr 2017 08:54:08 -0700 [thread overview]
Message-ID: <20170424155408.GA60835@samitolvanen.mtv.corp.google.com> (raw)
In-Reply-To: <76b0b4ab-f811-7c8e-c88c-1210a0e67119@gmail.com>
On Mon, Apr 24, 2017 at 10:05:03AM +0200, Milan Broz wrote:
> Isn't one of the goal of integrity checking to PREVENT that userspace
> accesses tampered data?
Absolutely. It's not acceptable for dm-verity to return unverified data
to userspace in restart mode.
Sami
next prev parent reply other threads:[~2017-04-24 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 7:34 [PATCH] dm verity: deferred hash checking for restart/logging mode Bongkyu Kim
2017-04-24 8:05 ` Milan Broz
2017-04-24 15:54 ` Sami Tolvanen [this message]
2017-04-24 9:58 ` kbuild test robot
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=20170424155408.GA60835@samitolvanen.mtv.corp.google.com \
--to=samitolvanen@google.com \
--cc=agk@redhat.com \
--cc=bongkyu.kim@lge.com \
--cc=dm-devel@redhat.com \
--cc=gmazyland@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=shli@kernel.org \
--cc=snitzer@redhat.com \
--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