[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <KL1PR0601MB4003E83BD65B8381C030FAC3BBF29@KL1PR0601MB4003.apcprd06.prod.outlook.com>
Date: Tue, 19 Apr 2022 03:22:31 +0000
From: 常凤楠 <changfengnan@...o.com>
To: Eric Biggers <ebiggers@...nel.org>
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
> -----Original Message-----
> From: Eric Biggers <ebiggers@...nel.org>
> Sent: Tuesday, April 19, 2022 11:19 AM
> To: 常凤楠 <changfengnan@...o.com>
> Cc: jaegeuk@...nel.org; chao@...nel.org; tytso@....edu;
> adilger.kernel@...ger.ca; axboe@...nel.dk; linux-block@...r.kernel.org;
> linux-ext4@...r.kernel.org; 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").
Oh, I see, thanks a lot.
>
> - Eric
Powered by blists - more mailing lists