linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nhat Pham <nphamcs@gmail.com>
To: Barry Song <21cnbao@gmail.com>
Cc: minchan@kernel.org, senozhatsky@chromium.org,
	akpm@linux-foundation.org,  linux-mm@kvack.org,
	ddstreet@ieee.org, sjenning@redhat.com,
	 vitaly.wool@konsulko.com, linux-kernel@vger.kernel.org,
	chriscli@google.com,  chrisl@kernel.org, hannes@cmpxchg.org,
	yosryahmed@google.com,  zhouchengming@bytedance.com,
	Barry Song <v-songbaohua@oppo.com>
Subject: Re: [PATCH] mm: zsmalloc: return -ENOSPC rather than -EINVAL in zs_malloc while size is too large
Date: Thu, 28 Dec 2023 11:19:08 -0800	[thread overview]
Message-ID: <CAKEwX=Njnwzf-TRTOp_L0wvzGnH+kQb8HJ9x_b6vt+FncOhgWw@mail.gmail.com> (raw)
In-Reply-To: <20231228061802.25280-1-v-songbaohua@oppo.com>

On Wed, Dec 27, 2023 at 10:18 PM Barry Song <21cnbao@gmail.com> wrote:
>
> This is the case the "compressed" data is larger than the original data,
> it is better to return -ENOSPC which can help zswap record a poor compr
> rather than an invalid request. Then we get more friendly counting for
> reject_compress_poor in debugfs.
>
>  bool zswap_store(struct folio *folio)
>  {
>         ...
>         ret = zpool_malloc(zpool, dlen, gfp, &handle);
>         if (ret == -ENOSPC) {
>                 zswap_reject_compress_poor++;
>                 goto put_dstmem;
>         }
>         if (ret) {
>                 zswap_reject_alloc_fail++;
>                 goto put_dstmem;
>         }
>         ...
>  }
>
> Also, zbud_alloc() and z3fold_alloc() are returning ENOSPC in the same
> case, eg
>  static int z3fold_alloc(struct z3fold_pool *pool, size_t size, gfp_t gfp,
>                         unsigned long *handle)
>  {
>         ...
>         if (!size || (gfp & __GFP_HIGHMEM))
>                 return -EINVAL;
>
>         if (size > PAGE_SIZE)
>                 return -ENOSPC;
>         ...
>  }
>
> Signed-off-by: Barry Song <v-songbaohua@oppo.com>
> ---
>  mm/zsmalloc.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
> index b1c0dad7f4cf..c937635e0ad1 100644
> --- a/mm/zsmalloc.c
> +++ b/mm/zsmalloc.c
> @@ -1364,9 +1364,12 @@ unsigned long zs_malloc(struct zs_pool *pool, size_t size, gfp_t gfp)
>         int newfg;
>         struct zspage *zspage;
>
> -       if (unlikely(!size || size > ZS_MAX_ALLOC_SIZE))
> +       if (unlikely(!size))
>                 return (unsigned long)ERR_PTR(-EINVAL);
>
> +       if (unlikely(size > ZS_MAX_ALLOC_SIZE))
> +               return (unsigned long)ERR_PTR(-ENOSPC);
> +
>         handle = cache_alloc_handle(pool, gfp);
>         if (!handle)
>                 return (unsigned long)ERR_PTR(-ENOMEM);
> --
> 2.34.1
>

LGTM.
Reviewed-by: Nhat Pham <nphamcs@gmail.com>


      parent reply	other threads:[~2023-12-28 19:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-28  6:18 Barry Song
2023-12-28  6:23 ` Chengming Zhou
2023-12-28 19:19 ` Nhat Pham [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='CAKEwX=Njnwzf-TRTOp_L0wvzGnH+kQb8HJ9x_b6vt+FncOhgWw@mail.gmail.com' \
    --to=nphamcs@gmail.com \
    --cc=21cnbao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=chriscli@google.com \
    --cc=chrisl@kernel.org \
    --cc=ddstreet@ieee.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=senozhatsky@chromium.org \
    --cc=sjenning@redhat.com \
    --cc=v-songbaohua@oppo.com \
    --cc=vitaly.wool@konsulko.com \
    --cc=yosryahmed@google.com \
    --cc=zhouchengming@bytedance.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