linux-kernel - Re: (subset) [PATCH 00/20] 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] [day] [month] [year] [list]

Message-Id: <176607686430.264355.9361744176497178325.b4-ty@kernel.dk>
Date: Thu, 18 Dec 2025 09:54:24 -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>
Subject: Re: (subset) [PATCH 00/20] ublk: add support for integrity data


On Tue, 16 Dec 2025 22:34:34 -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/20] block: validate pi_offset integrity limit
        commit: ccb8a3c08adf8121e2afb8e704f007ce99324d79
[02/20] block: validate interval_exp integrity limit
        commit: af65faf34f6e9919bdd2912770d25d2a73cbcc7c

Best regards,
-- 
Jens Axboe