Re: [PATCH for-next v2 1/2] block: introduce pi_size field in blk_integrity

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Anuj Gupta <anuj20.g@xxxxxxxxxxx>
Subject: Re: [PATCH for-next v2 1/2] block: introduce pi_size field in blk_integrity
From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
Date: Thu, 05 Jun 2025 21:51:38 -0400
Cc: vincent.fu@xxxxxxxxxxx, jack@xxxxxxx, anuj1072538@xxxxxxxxx, axboe@xxxxxxxxx, viro@xxxxxxxxxxxxxxxxxx, brauner@xxxxxxxxxx, hch@xxxxxxxxxxxxx, martin.petersen@xxxxxxxxxx, ebiggers@xxxxxxxxxx, adilger@xxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, joshi.k@xxxxxxxxxxx
In-reply-to: <20250605150729.2730-2-anuj20.g@samsung.com> (Anuj Gupta's message of "Thu, 5 Jun 2025 20:37:28 +0530")
Organization: Oracle Corporation

Anuj,

> Introduce a new pi_size field in struct blk_integrity to explicitly
> represent the size (in bytes) of the protection information (PI) tuple.
> This is a prep patch.

LGTM.

Reviewed-by: Martin K. Petersen <martin.petersen@xxxxxxxxxx>

-- 
Martin K. Petersen

References:
- [PATCH for-next v2 0/2] add ioctl to query protection info capabilities
  - From: Anuj Gupta
- [PATCH for-next v2 1/2] block: introduce pi_size field in blk_integrity
  - From: Anuj Gupta

Prev by Date: Re: [PATCH 1/7] mm: shmem: correctly pass alloced parameter to shmem_recalc_inode() to avoid WARN_ON()
Next by Date: Re: [PATCH] proc: clear FMODE_LSEEK flag correctly for permanent pde
Previous by thread: [PATCH for-next v2 1/2] block: introduce pi_size field in blk_integrity
Next by thread: Re: [PATCH for-next v2 1/2] block: introduce pi_size field in blk_integrity
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [NTFS 3] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [NTFS 3] [Samba] [Device Mapper] [CEPH Development]