From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753795AbbK0CSs (ORCPT ); Thu, 26 Nov 2015 21:18:48 -0500 Received: from mail-pa0-f47.google.com ([209.85.220.47]:33454 "EHLO mail-pa0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753692AbbK0CSo (ORCPT ); Thu, 26 Nov 2015 21:18:44 -0500 Date: Fri, 27 Nov 2015 11:19:45 +0900 From: Sergey Senozhatsky To: Minchan Kim Cc: Andrew Morton , Kyeongdon Kim , linux-kernel@vger.kernel.org, Sergey Senozhatsky , Sergey Senozhatsky Subject: Re: [PATCH v2 3/3] zram: pass gfp from zcomp frontend to backend Message-ID: <20151127021945.GB4220@swordfish> References: <1448430673-10766-3-git-send-email-minchan@kernel.org> <20151127020510.GA4220@swordfish> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151127020510.GA4220@swordfish> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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