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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 18 Apr 2022 20:18:50 -0700 From: Eric Biggers <ebiggers@...nel.org> To: 常凤楠 <changfengnan@...o.com> Cc: "jaegeuk@...nel.org" <jaegeuk@...nel.org>, "chao@...nel.org" <chao@...nel.org>, "tytso@....edu" <tytso@....edu>, "adilger.kernel@...ger.ca" <adilger.kernel@...ger.ca>, "axboe@...nel.dk" <axboe@...nel.dk>, "linux-block@...r.kernel.org" <linux-block@...r.kernel.org>, "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>, "linux-f2fs-devel@...ts.sourceforge.net" <linux-f2fs-devel@...ts.sourceforge.net> Subject: Re: [PATCH 2/3] f2fs: notify when device not supprt inlinecrypt On Tue, Apr 19, 2022 at 03:14:51AM +0000, 常凤楠 wrote: > > Thanks for your explanation, this patchset has too many case to forget to handle... > Back to my first thought, maybe there should have one sysfs node to indicate the > device support inlinecrypt or not ? So user can know it's device not support inlinecrypt > and not for other reasons. > Linux v5.18 has that. See https://git.kernel.org/linus/20f01f1632036660 ("blk-crypto: show crypto capabilities in sysfs"). - Eric
Powered by blists - more mailing lists