From: Andrew Morton <akpm@linux-foundation.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Brian Geffon <bgeffon@google.com>,
Minchan Kim <minchan@kernel.org>,
Richard Chang <richardycc@google.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/2] zram: writeback fixes
Date: Mon, 25 May 2026 14:31:27 -0700 [thread overview]
Message-ID: <20260525143127.9f8ff15e31df71bdb494ab61@linux-foundation.org> (raw)
In-Reply-To: <20260525044639.1888561-1-senozhatsky@chromium.org>
On Mon, 25 May 2026 13:46:00 +0900 Sergey Senozhatsky <senozhatsky@chromium.org> wrote:
> Brian reported several issues with zram's writeback implementation.
> This small series addresses those issues.
I hate to go all bureaucratic, but there's quite a lot missing here,
and it's rather important, to some. It's all about taking care of
people who are using kernels prior to 7.2 (or 7.1).
- Link: to Brian's reports?
- Description of user-visible runtime effects of the bugs?
- Fixes: targets?
- Decision on whether we should backport the fixes into earlier kernels?
Anyway, I'll queue these in mm-new, but please give some thought to the
above?
Also, AI review didn't find anything to complain about with these
changes, but it might have found a pre-existing issue:
https://sashiko.dev/#/patchset/20260525044639.1888561-1-senozhatsky@chromium.org
Thanks.
next prev parent reply other threads:[~2026-05-25 21:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 4:46 Sergey Senozhatsky
2026-05-25 4:46 ` [PATCH 1/2] zram: do not leak blk idx at the end of writeback Sergey Senozhatsky
2026-05-25 4:46 ` [PATCH 2/2] zram: clear trailing bytes of compressed writeback pages Sergey Senozhatsky
2026-05-25 21:31 ` Andrew Morton [this message]
2026-05-26 2:33 ` [PATCH 0/2] zram: writeback fixes 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=20260525143127.9f8ff15e31df71bdb494ab61@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bgeffon@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=richardycc@google.com \
--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®