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
| ||
|
Message-ID: <7c00f4f8-5bdf-4fa6-d9f0-141cf88c9ec9@nvidia.com> Date: Mon, 27 Mar 2023 22:18:20 +0000 From: Chaitanya Kulkarni <chaitanyak@...dia.com> To: Akinobu Mita <akinobu.mita@...il.com> CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Christoph Hellwig <hch@...radead.org>, "linux-block@...r.kernel.org" <linux-block@...r.kernel.org>, "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>, "axboe@...nel.dk" <axboe@...nel.dk> Subject: Re: [PATCH 0/2] block: null_blk: make fault-injection configurable via configfs On 3/27/23 15:13, Christoph Hellwig wrote: > On Mon, Mar 27, 2023 at 11:37:31PM +0900, Akinobu Mita wrote: >> This patch set makes null_blk driver-specific fault-injection dynamically >> configurable per device via configfs. >> >> Since the null_blk driver supports configuration such as device creation >> via configfs, it is natural to configure fault-injection via configfs as >> well. >> >> Currently, only the debugfs interface is provided for dynamically >> configuring fault-injection, so this introduces a compatible interface via >> configfs. > Oh, nice. Can you also update blktests to take advantage of this and > not require built-in null_blk for fault injection tests? +1 on blktests, please CC me when you do. -ck
Powered by blists - more mailing lists