From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
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: Tue, 26 May 2026 11:33:09 +0900 [thread overview]
Message-ID: <ahUFMBcjHlhJMF8p@google.com> (raw)
In-Reply-To: <20260525143127.9f8ff15e31df71bdb494ab61@linux-foundation.org>
On (26/05/25 14:31), Andrew Morton 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).
Sorry, Andrew, it was just me being lazy.
> - 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?
I updated commit messages and sent out v2. The reports are private,
so on public links. Both issues are low risk.
[..]
> 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
Correct, a pre-existing issue (first appeared in v6.19), we fix it in this
series. The theoretical data leak issue first appeared in v7.0.
prev parent reply other threads:[~2026-05-26 2:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 4:46 [PATCH 0/2] zram: writeback fixes 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 ` [PATCH 0/2] zram: writeback fixes Andrew Morton
2026-05-26 2:33 ` 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=ahUFMBcjHlhJMF8p@google.com \
--to=senozhatsky@chromium.org \
--cc=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 \
/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.