From: Andrew Morton <akpm@linux-foundation.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: linux-kernel@vger.kernel.org, Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [PATCH] zram: do not skip the first bucket
Date: Tue, 1 Oct 2024 14:57:39 -0700 [thread overview]
Message-ID: <20241001145739.8afe344d456d90fb6e8d96d6@linux-foundation.org> (raw)
In-Reply-To: <20241001085634.1948384-1-senozhatsky@chromium.org>
On Tue, 1 Oct 2024 17:55:56 +0900 Sergey Senozhatsky <senozhatsky@chromium.org> wrote:
> A small fixup.
>
> ...
>
> --- a/drivers/block/zram/zram_drv.c
> +++ b/drivers/block/zram/zram_drv.c
> @@ -264,7 +264,7 @@ static struct zram_pp_slot *select_pp_slot(struct zram_pp_ctl *ctl)
> s32 idx = NUM_PP_BUCKETS - 1;
>
> /* The higher the bucket id the more optimal slot post-processing is */
> - while (idx > 0) {
> + while (idx >= 0) {
> pps = list_first_entry_or_null(&ctl->pp_buckets[idx],
> struct zram_pp_slot,
> entry);
I hate to be a kernel bureaucrat, but there's a lot missing from this
changelog!
a) What are the user-visible runtime effects?
b) What is the Fixes:
c) Is a cc:stable needed? If so, a) is super-relevant.
oh, it's a fix against the mm-unstable patch "zram: rework recompress
target selection strategy". That's new information! Please disregard
the above.
d) what was wrong with the original code? And still a).
> Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
e) what did Dan report ("Closes:")?
Sorry, but this is all stuff which you easily had available but which I
had to figure out. And which I now present to other readers so they
needn't figure it out. That would be inefficient!
Ho hum, anyway, thanks, applied as an effectively unchangelogged fix
against mm-unstable's "zram: rework recompress target selection
strategy".
next prev parent reply other threads:[~2024-10-01 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240925005315.89E59C4CEC4@smtp.kernel.org>
2024-10-01 8:55 ` Sergey Senozhatsky
2024-10-01 21:57 ` Andrew Morton [this message]
2024-10-02 1:29 ` 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=20241001145739.8afe344d456d90fb6e8d96d6@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=senozhatsky@chromium.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
all inboxes | Powered by JetHome®