[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220603173815.803602103@linuxfoundation.org>
Date: Fri, 3 Jun 2022 19:39:52 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-kernel@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
stable@...r.kernel.org,
Sarthak Kukreti <sarthakkukreti@...gle.com>,
Kees Cook <keescook@...omium.org>,
Mike Snitzer <snitzer@...nel.org>
Subject: [PATCH 4.19 24/30] dm verity: set DM_TARGET_IMMUTABLE feature flag
From: Sarthak Kukreti <sarthakkukreti@...gle.com>
commit 4caae58406f8ceb741603eee460d79bacca9b1b5 upstream.
The device-mapper framework provides a mechanism to mark targets as
immutable (and hence fail table reloads that try to change the target
type). Add the DM_TARGET_IMMUTABLE flag to the dm-verity target's
feature flags to prevent switching the verity target with a different
target type.
Fixes: a4ffc152198e ("dm: add verity target")
Cc: stable@...r.kernel.org
Signed-off-by: Sarthak Kukreti <sarthakkukreti@...gle.com>
Reviewed-by: Kees Cook <keescook@...omium.org>
Signed-off-by: Mike Snitzer <snitzer@...nel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
---
drivers/md/dm-verity-target.c | 1 +
1 file changed, 1 insertion(+)
--- a/drivers/md/dm-verity-target.c
+++ b/drivers/md/dm-verity-target.c
@@ -1176,6 +1176,7 @@ bad:
static struct target_type verity_target = {
.name = "verity",
+ .features = DM_TARGET_IMMUTABLE,
.version = {1, 4, 0},
.module = THIS_MODULE,
.ctr = verity_ctr,
Powered by blists - more mailing lists