| 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: Thu, 26 Nov 2015 00:04:49 +0900 From: Sergey Senozhatsky <sergey.senozhatsky@...il.com> To: Minchan Kim <minchan@...nel.org> Cc: Sergey Senozhatsky <sergey.senozhatsky@...il.com>, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, Kyeongdon Kim <kyeongdon.kim@....com> Subject: Re: [PATCH v2 3/3] zram: pass gfp from zcomp frontend to backend Hello, On (11/25/15 22:50), Minchan Kim wrote: [..] > > I think that applying 3/3 before 2/3 will be a simpler (and probably a better) > > thing to do. We fitst extend zcomp interface and pass flags (without any > > functional change) and then extend the flags and introduce vmalloc fallback. > > The reason I ordered such way is that I wanted to discuss [2/3] as > stable material after I get your ACK. It solves real problem in android platform > which is real fact and I think it's enough small to send stable tree. > What do you think? > > > > > So we don't have to add comments to lz4/lzo backend that are getting (re-)moved > > in the very next commit. > > Fair enough if you don't agree sending [2/3] to stable. Aha, I see. I don't mind to send it to -stable (with __GFP_HIGHMEM fix up). Do -stable guys take this type of patches? -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