From: Ankit Kumar <ankit.kumar@samsung.com>
To: Jens Axboe <axboe@kernel.dk>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Keith Busch <kbusch@kernel.org>
Cc: gost.dev@samsung.com, Ankit Kumar <ankit.kumar@samsung.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] block:t10-pi: remove redundant Type2 check during t10 PI verify
Date: Fri, 11 Aug 2023 21:03:12 +0530 [thread overview]
Message-ID: <20230811153313.93786-2-ankit.kumar@samsung.com> (raw)
In-Reply-To: <20230811153313.93786-1-ankit.kumar@samsung.com>
T10_PI_TYPE2_PROTECTION is neither used to generate nor verify
crc and ip. Remove this redundant check.
Signed-off-by: Ankit Kumar <ankit.kumar@samsung.com>
---
block/t10-pi.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/block/t10-pi.c b/block/t10-pi.c
index 914d8cddd43a..bf0bba01417f 100644
--- a/block/t10-pi.c
+++ b/block/t10-pi.c
@@ -64,8 +64,7 @@ static blk_status_t t10_pi_verify(struct blk_integrity_iter *iter,
struct t10_pi_tuple *pi = iter->prot_buf;
__be16 csum;
- if (type == T10_PI_TYPE1_PROTECTION ||
- type == T10_PI_TYPE2_PROTECTION) {
+ if (type == T10_PI_TYPE1_PROTECTION) {
if (pi->app_tag == T10_PI_APP_ESCAPE)
goto next;
--
2.25.1
next prev parent reply other threads:[~2023-08-11 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230811101910epcas5p30f4711f8d7da7bcb716d3a4d71978859@epcas5p3.samsung.com>
2023-08-11 15:33 ` [PATCH 0/2] Small fixes for block t10-pi Ankit Kumar
2023-08-11 15:33 ` Ankit Kumar [this message]
2023-08-14 1:19 ` [PATCH 1/2] block:t10-pi: remove redundant Type2 check during t10 PI verify Martin K. Petersen
2023-08-11 15:33 ` [PATCH 2/2] block:t10-pi: remove duplicate module license Ankit Kumar
2023-08-14 1:19 ` Martin K. Petersen
2023-08-22 11:52 ` [PATCH 0/2] Small fixes for block t10-pi Ankit Kumar
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=20230811153313.93786-2-ankit.kumar@samsung.com \
--to=ankit.kumar@samsung.com \
--cc=axboe@kernel.dk \
--cc=gost.dev@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.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