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: Fri, 27 Nov 2015 11:19:45 +0900 From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com> To: Minchan Kim <minchan@...nel.org> Cc: Andrew Morton <akpm@...ux-foundation.org>, Kyeongdon Kim <kyeongdon.kim@....com>, linux-kernel@...r.kernel.org, Sergey Senozhatsky <sergey.senozhatsky@...il.com>, Sergey Senozhatsky <sergey.senozhatsky.work@...il.com> Subject: Re: [PATCH v2 3/3] zram: pass gfp from zcomp frontend to backend On (11/27/15 11:05), Sergey Senozhatsky wrote: > Minchan Kim wrote: > [..] > > +static struct zcomp_strm *zcomp_strm_alloc(struct zcomp *comp, gfp_t flags) > > { > > + zstrm = zcomp_strm_alloc(comp, GFP_NOIO|__GFP_NORETRY| > > + __GFP_NOWARN|__GFP_NOMEMALLOC); > > > and it seems that after 3/3 (v2) we also lost GFP_ZERO for private > allocation. kzalloc->kmalloc, and no explicit __GFP_ZERO for __vmalloc(). > well, we probably don't really need __GFP_ZERO for ->private, but let's address it in a separate patch, not as an undocumented change. -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