[PATCH] fsverity: remove inode from fsverity_verification_ctx

[Eric Biggers <ebiggers@kernel.org>]

This field is no longer used, so remove it.

Signed-off-by: Eric Biggers <ebiggers@kernel.org>
---
 fs/verity/verify.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/fs/verity/verify.c b/fs/verity/verify.c
index 37e000f01c180..31797f9b24d0f 100644
--- a/fs/verity/verify.c
+++ b/fs/verity/verify.c
@@ -17,11 +17,10 @@ struct fsverity_pending_block {
 	u64 pos;
 	u8 real_hash[FS_VERITY_MAX_DIGEST_SIZE];
 };
 
 struct fsverity_verification_context {
-	struct inode *inode;
 	struct fsverity_info *vi;
 
 	/*
 	 * This is the queue of data blocks that are pending verification.  When
 	 * the crypto layer supports interleaved hashing, we allow multiple
@@ -314,11 +313,10 @@ static bool verify_data_block(struct fsverity_info *vi,
 
 static void
 fsverity_init_verification_context(struct fsverity_verification_context *ctx,
 				   struct fsverity_info *vi)
 {
-	ctx->inode = vi->inode;
 	ctx->vi = vi;
 	ctx->num_pending = 0;
 	if (vi->tree_params.hash_alg->algo_id == HASH_ALGO_SHA256 &&
 	    sha256_finup_2x_is_optimized())
 		ctx->max_pending = 2;

base-commit: ada3a1a48d5a21a78c1460c8853502d13062ffc9
-- 
2.52.0