stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: stable@vger.kernel.org, Minchan Kim <minchan@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Kyeongdon Kim <kyeongdon.kim@lge.com>,
	linux-kernel@vger.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [stable] upstream 3d5fe03a3ea01 -stable backport request
Date: Mon, 25 Jan 2016 22:01:20 +0900	[thread overview]
Message-ID: <20160125130120.GD526@swordfish> (raw)
In-Reply-To: <20160125124654.GA526@swordfish>

On (01/25/16 21:46), Sergey Senozhatsky wrote:
> 
> Hello,
> 
> Please add upstream 'commit 3d5fe03a3ea01 ("zram/zcomp: use
> GFP_NOIO to allocate streams")' to stable releases.
> 

[v3.15+]

	-ss

> 
> :commit 3d5fe03a3ea013060ebba2a811aeb0f23f56aefa
> :Author: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> :
> :    zram/zcomp: use GFP_NOIO to allocate streams
> :    
> :    We can end up allocating a new compression stream with GFP_KERNEL from
> :    within the IO path, which may result is nested (recursive) IO
> :    operations.  That can introduce problems if the IO path in question is a
> :    reclaimer, holding some locks that will deadlock nested IOs.
> :    
> :    Allocate streams and working memory using GFP_NOIO flag, forbidding
> :    recursive IO and FS operations.
> 
> 
> 	-ss
> 

      reply	other threads:[~2016-01-25 13:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 12:46 [stable] upstream 3d5fe03a3ea01 -stable backport request Sergey Senozhatsky
2016-01-25 13:01 ` Sergey Senozhatsky [this message]

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=20160125130120.GD526@swordfish \
    --to=sergey.senozhatsky@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=kyeongdon.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=stable@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).