| 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
| ||
|
Date: Tue, 1 Sep 2015 10:41:50 +0900 From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com> To: Minchan Kim <minchan@...nel.org> Cc: Sergey Senozhatsky <sergey.senozhatsky@...il.com>, Joonsoo Kim <js1304@...il.com>, Andrew Morton <akpm@...ux-foundation.org>, Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>, linux-kernel@...r.kernel.org, Joonsoo Kim <iamjoonsoo.kim@....com> Subject: Re: [PATCH 0/2] prepare zram for crypto api-powered zcomp Hello Minchan, On (09/01/15 10:22), Minchan Kim wrote: > Hello Sergey, > > On Fri, Aug 28, 2015 at 05:02:12AM -0700, Sergey Senozhatsky wrote: > > Hi, > > > > I think those are the changes we need to do in zram. The rest > > is zcomp specific. I'll be quite surprised to find out that > > we need to change (in zram_drv) more. > > This patchset looks good to me. > > Sergey, > Is there any patches you will send to clean up zram_drv to > support crypto? Hm... Probably no. The patch set makes zram ready for any zcomp rework/redesign; the rest must be handled in zcomp/crypto. At least for the time being I can't think of any additional tweaks in zram_drv. > If so, I'd like to see it and sort it out first. Then, Joonsoo > will work crypto support based on it. -ss -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists