public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Kyeongdon Kim <kyeongdon.kim@lge.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	ngupta@vflare.org, linux-kernel@vger.kernel.org,
	sergey.senozhatsky@gmail.com, sergey.senozhatsky.work@gmail.com
Subject: Re: [PATCH v2] zram: Prevent page allocation failure during zcomp_strm_alloc
Date: Mon, 23 Nov 2015 12:35:11 +0900	[thread overview]
Message-ID: <20151123033511.GB7449@swordfish> (raw)
In-Reply-To: <20151123031400.GA7449@swordfish>

On (11/23/15 12:14), Sergey Senozhatsky wrote:
> 
> yes, GFP_KERNEL looks a bit fragile to me too. And may be zcomp_strm_alloc()
> and comp->backend->create() deserve GFP_NOFS. I believe I sent a patch doing
> this a while ago: https://lkml.org/lkml/2015/6/16/465
>

perhaps just __GFP_RECLAIM (GFP_NOIO), not  '__GFP_RECLAIM | __GFP_IO'
(GFP_NOFS), is better.

	-ss

  reply	other threads:[~2015-11-23  3:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 10:02 [PATCH v2] zram: Prevent page allocation failure during zcomp_strm_alloc Kyeongdon Kim
2015-11-21  2:10 ` Sergey Senozhatsky
2015-11-21  2:15   ` Sergey Senozhatsky
2015-11-21  9:37     ` Sergey Senozhatsky
2015-11-23  2:15 ` Minchan Kim
2015-11-23  3:14   ` Sergey Senozhatsky
2015-11-23  3:35     ` Sergey Senozhatsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-11-23  4:18 Minchan Kim
2015-11-23  7:43 ` Sergey Senozhatsky
2015-11-23  8:13   ` Sergey Senozhatsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151123033511.GB7449@swordfish \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=kyeongdon.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=ngupta@vflare.org \
    --cc=sergey.senozhatsky@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox