All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: stable@vger.kernel.org,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Minchan Kim <minchan@kernel.org>, Nitin Gupta <ngupta@vflare.org>,
	Alexey Romanov <avromanov@sberdevices.ru>,
	Dmitry Rokosov <ddrokosov@sberdevices.ru>,
	Lukas Czerner <lczerner@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 5.19] Revert "zram: remove double compression logic"
Date: Mon, 29 Aug 2022 09:50:35 +0200	[thread overview]
Message-ID: <Ywxvy8+it4vyIyHz@kroah.com> (raw)
In-Reply-To: <20220829073147.10716-1-jslaby@suse.cz>

On Mon, Aug 29, 2022 at 09:31:47AM +0200, Jiri Slaby wrote:
> This reverts commit e7be8d1dd983156b ("zram: remove double compression
> logic") as it causes zram failures.  It does not revert cleanly, PTR_ERR
> handling was introduced in the meantime.  This is handled by appropriate
> IS_ERR.
> 
> When under memory pressure, zs_malloc() can fail.  Before the above
> commit, the allocation was retried with direct reclaim enabled (GFP_NOIO).
> After the commit, it is not -- only __GFP_KSWAPD_RECLAIM is tried.
> 
> So when the failure occurs under memory pressure, the overlaying
> filesystem such as ext2 (mounted by ext4 module in this case) can emit
> failures, making the (file)system unusable:
>   EXT4-fs warning (device zram0): ext4_end_bio:343: I/O error 10 writing to inode 16386 starting block 159744)
>   Buffer I/O error on device zram0, logical block 159744
> 
> With direct reclaim, memory is really reclaimed and allocation succeeds,
> eventually.  In the worst case, the oom killer is invoked, which is proper
> outcome if user sets up zram too large (in comparison to available RAM).
> 
> This very diff doesn't apply to 5.19 (stable) cleanly (see PTR_ERR note
> above). Use revert of e7be8d1dd983 directly.
> 
> Link: https://bugzilla.suse.com/show_bug.cgi?id=1202203
> Link: https://lkml.kernel.org/r/20220810070609.14402-1-jslaby@suse.cz
> Fixes: e7be8d1dd983 ("zram: remove double compression logic")
> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
> Reviewed-by: Sergey Senozhatsky <senozhatsky@chromium.org>
> Cc: Minchan Kim <minchan@kernel.org>
> Cc: Nitin Gupta <ngupta@vflare.org>
> Cc: Alexey Romanov <avromanov@sberdevices.ru>
> Cc: Dmitry Rokosov <ddrokosov@sberdevices.ru>
> Cc: Lukas Czerner <lczerner@redhat.com>
> Cc: <stable@vger.kernel.org>	[5.19]
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>  drivers/block/zram/zram_drv.c | 42 ++++++++++++++++++++++++++---------
>  drivers/block/zram/zram_drv.h |  1 +
>  2 files changed, 33 insertions(+), 10 deletions(-)
> 

Now queued up, thanks.

greg k-h

      reply	other threads:[~2022-08-29  7:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25 10:43 FAILED: patch "[PATCH] Revert "zram: remove double compression logic"" failed to apply to 5.19-stable tree gregkh
2022-08-29  7:31 ` [PATCH 5.19] Revert "zram: remove double compression logic" Jiri Slaby
2022-08-29  7:50   ` Greg KH [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=Ywxvy8+it4vyIyHz@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=avromanov@sberdevices.ru \
    --cc=ddrokosov@sberdevices.ru \
    --cc=jslaby@suse.cz \
    --cc=lczerner@redhat.com \
    --cc=minchan@kernel.org \
    --cc=ngupta@vflare.org \
    --cc=senozhatsky@chromium.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.