All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, minchan@kernel.org,
	bgeffon@google.com,  axboe@kernel.dk, senozhatsky@chromium.org
Subject: Re: + zram-use-gfp_kernel-for-post-processing-slot-allocation.patch added to mm-new branch
Date: Sun, 8 Mar 2026 19:28:04 +0900	[thread overview]
Message-ID: <aa1Oemm99ek7lUU0@google.com> (raw)
In-Reply-To: <20260306014923.BA31EC116C6@smtp.kernel.org>

On (26/03/05 17:49), Andrew Morton wrote:
> 
> The patch titled
>      Subject: zram: use GFP_KERNEL for post-processing slot allocation
> has been added to the -mm mm-new branch.  Its filename is
>      zram-use-gfp_kernel-for-post-processing-slot-allocation.patch
> 
> This patch will shortly appear at
>      https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/zram-use-gfp_kernel-for-post-processing-slot-allocation.patch

[..]

> 
> Post-processing slot allocation used to be performed under slot bit-lock,
> so gfp was restricted, then we switched to a sleepable slot lock but gpf
> still remained restricted.  Drop that restriction and use GFP_KERNEL
> instead.
> 
> Link: https://lkml.kernel.org/r/20260305021619.617481-1-senozhatsky@chromium.org
> Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org>
> Acked-by: Brian Geffon <bgeffon@google.com>
> Cc: Jens Axboe <axboe@kernel.dk>
> Cc: Minchan Kim <minchan@kernel.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
> 
>  drivers/block/zram/zram_drv.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --- a/drivers/block/zram/zram_drv.c~zram-use-gfp_kernel-for-post-processing-slot-allocation
> +++ a/drivers/block/zram/zram_drv.c
> @@ -297,7 +297,7 @@ static bool place_pp_slot(struct zram *z
>  	struct zram_pp_slot *pps;
>  	u32 bid;
>  
> -	pps = kmalloc_obj(*pps, GFP_NOIO | __GFP_NOWARN);
> +	pps = kmalloc_obj(*pps, GFP_KERNEL | __GFP_NOWARN);
>  	if (!pps)
>  		return false;

Right... that was silly.
Andrew, can you please drop this patch?  We cannot reclaim memory
in place_pp_slot(), because it's called under slot-lock, which is
IO lock for zram.  We cannot re-enter zram under IO lock, so we have
to keep using GFP_NOIO here.

      reply	other threads:[~2026-03-08 10:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06  1:49 + zram-use-gfp_kernel-for-post-processing-slot-allocation.patch added to mm-new branch Andrew Morton
2026-03-08 10:28 ` 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=aa1Oemm99ek7lUU0@google.com \
    --to=senozhatsky@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=bgeffon@google.com \
    --cc=minchan@kernel.org \
    --cc=mm-commits@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.