linux-kernel - Re: [PATCH v4 00/19] ublk: add support for integrity data

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <176823494699.210978.11786417520987003965.b4-ty@kernel.dk>
Date: Mon, 12 Jan 2026 09:22:26 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Ming Lei <ming.lei@...hat.com>, Shuah Khan <shuah@...nel.org>, 
 Caleb Sander Mateos <csander@...estorage.com>
Cc: linux-block@...r.kernel.org, linux-kselftest@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Stanley Zhang <stazhang@...estorage.com>, 
 Uday Shankar <ushankar@...estorage.com>, 
 "Martin K . Petersen" <martin.petersen@...cle.com>
Subject: Re: [PATCH v4 00/19] ublk: add support for integrity data


On Thu, 08 Jan 2026 02:19:28 -0700, Caleb Sander Mateos wrote:
> Much work has recently gone into supporting block device integrity data
> (sometimes called "metadata") in Linux. Many NVMe devices these days
> support metadata transfers and/or automatic protection information
> generation and verification. However, ublk devices can't yet advertise
> integrity data capabilities. This patch series wires up support for
> integrity data in ublk. The ublk feature is referred to as "integrity"
> rather than "metadata" to match the block layer's name for it and to
> avoid confusion with the existing and unrelated UBLK_IO_F_META.
> 
> [...]

Applied, thanks!

[01/19] blk-integrity: take const pointer in blk_integrity_rq()
        commit: 835042fb1971b1cc6acb46d53b8862643fd7d0a8
[02/19] ublk: move ublk flag check functions earlier
        commit: e859e7c26a5c4689083f161a52d039b9b454e403
[03/19] ublk: support UBLK_PARAM_TYPE_INTEGRITY in device creation
        commit: 98bf2256855eb682433a33e6a7c4bce35191ca99
[04/19] ublk: set UBLK_IO_F_INTEGRITY in ublksrv_io_desc
        commit: f82f0a16a8270b17211254beeb123d11a0f279cd
[05/19] ublk: split out ublk_copy_user_bvec() helper
        commit: fc652d415cd8b45e9a534d1c019da175cca4c95a
[06/19] ublk: split out ublk_user_copy() helper
        commit: 5bfbbc9938f5dee7f252ef05f47b9a26f05f281a
[07/19] ublk: inline ublk_check_and_get_req() into ublk_user_copy()
        commit: ca80afd8708fa22f6d3a1e0306ae12a64e5291b5
[08/19] ublk: move offset check out of __ublk_check_and_get_req()
        commit: fd5a005fa6a261762292a2d89ef8d0174b66f541
[09/19] ublk: implement integrity user copy
        commit: be82a89066d595da334f6e153ababcedc3f92ad6
[10/19] ublk: support UBLK_F_INTEGRITY
        commit: b2503e936b598b993cb09005194dc77d2fa3f082
[11/19] ublk: optimize ublk_user_copy() on daemon task
        commit: bfe1255712a3b1c1f7418c5504a1bf53735d3848
[12/19] selftests: ublk: display UBLK_F_INTEGRITY support
        commit: c1d7c0f9cdf6690eff4518f1c17a37d5ee647cd1
[13/19] selftests: ublk: add utility to get block device metadata size
        commit: 261b67f4e34716e793b0b95d2722b2fe780ed5f4
[14/19] selftests: ublk: add kublk support for integrity params
        commit: 6ed6476c4aefa9ee3ba90f39bcc002dd034f6e03
[15/19] selftests: ublk: implement integrity user copy in kublk
        commit: 24f8a44b797f03dfadb455138930523599d3c22a
[16/19] selftests: ublk: support non-O_DIRECT backing files
        commit: a1805442674b85ff9d626965f828e4fd71a82b28
[17/19] selftests: ublk: add integrity data support to loop target
        commit: f48250dc5ba8368ccb587093eb20d1c7baecaacf
[18/19] selftests: ublk: add integrity params test
        commit: 9e9f635525b12f055558a7cfe2e54d109839d030
[19/19] selftests: ublk: add end-to-end integrity test
        commit: 78796b6bae8684b753b658f431b5b1ee24300d64

Best regards,
-- 
Jens Axboe