From: Andrew Morton <akpm@linux-foundation.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Minchan Kim <minchan@kernel.org>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
linux-mm@kvack.org, Brian Geffon <bgeffon@google.com>
Subject: Re: [PATCH 1/5] zram: do not autocorrect bad recompression parameters
Date: Mon, 2 Mar 2026 20:28:12 -0800 [thread overview]
Message-ID: <20260302202812.06e4fd4156e5315f0b5f3fad@linux-foundation.org> (raw)
In-Reply-To: <bg7ivz7ajiuzdbpv3h6hbptxgmqk5fhwakw4rzk4sz3bczky5a@rde3y352n5ej>
On Tue, 3 Mar 2026 11:59:45 +0900 Sergey Senozhatsky <senozhatsky@chromium.org> wrote:
> Sorry for the delay.
>
> On (26/02/28 12:05), Andrew Morton wrote:
> > On Fri, 27 Feb 2026 17:21:07 +0900 Sergey Senozhatsky <senozhatsky@chromium.org> wrote:
> > >
> >
> > A nice [0/N] overview would be appropriate for a 5-patch series, please.
>
> Well... I couldn't come up with a nice overview, let me try.
>
>
> The series is based on internal discussions. Minchan looked at
> recompression recently and pointed out a few things that he thought
> were confusing or unexpected/unintuitive, like the fact that zram
> would autocorrect bad recompression priority parameter, or some
> other assumptions that zram made. I couldn't explain why it was
> like that, and just agreed that it was confusing. The final patch
> in the series removes chained recompression, which also has some
> unexpected behavior, so I just decided to simplify the code and
> remove that feature.
OK, thanks, I did this:
From: Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: zram: do not autocorrect bad recompression parameters
Date: Fri, 27 Feb 2026 17:21:07 +0900
Patch series "zram: various cleanups".
The series is based on internal discussions. Minchan looked at
recompression recently and pointed out a few things that he thought
were confusing or unexpected/unintuitive, like the fact that zram
would autocorrect bad recompression priority parameter, or some
other assumptions that zram made. I couldn't explain why it was
like that, and just agreed that it was confusing. The final patch
in the series removes chained recompression, which also has some
unexpected behavior, so I just decided to simplify the code and
remove that feature.
This patch (of 5):
Do not silently autocorrect bad recompression priority parameter value and
just error out.
Link: https://lkml.kernel.org/r/bg7ivz7ajiuzdbpv3h6hbptxgmqk5fhwakw4rzk4sz3bczky5a@rde3y352n5ej
Link: https://lkml.kernel.org/r/8a5d53d19a8dbd51d7d81d153676895163e0735e.1772180459.git.senozhatsky@chromium.org
Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org>
Suggested-by: Minchan Kim <minchan@kernel.org>
Cc: Brian Geffon <bgeffon@google.com>
Cc: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
Cc: Jens Axboe <axboe@kernel.dk>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Lars Ellenberg <lars.ellenberg@linbit.com>
Cc: Philipp Reisner <philipp.reisner@linbit.com>
Cc: Shuah Khan <skhan@linuxfoundation.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ...
prev parent reply other threads:[~2026-03-03 4:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 8:21 Sergey Senozhatsky
2026-02-27 8:21 ` [PATCH 2/5] zram: drop ->num_active_comps Sergey Senozhatsky
2026-02-27 8:21 ` [PATCH 3/5] zram: recompression priority param should override algo Sergey Senozhatsky
2026-02-27 8:21 ` [PATCH 4/5] zram: update recompression documentation Sergey Senozhatsky
2026-02-27 8:21 ` [PATCH 5/5] zram: remove chained recompression Sergey Senozhatsky
2026-02-28 20:05 ` [PATCH 1/5] zram: do not autocorrect bad recompression parameters Andrew Morton
2026-03-03 2:59 ` Sergey Senozhatsky
2026-03-03 4:28 ` Andrew Morton [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=20260302202812.06e4fd4156e5315f0b5f3fad@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bgeffon@google.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@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