From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by smtp.subspace.kernel.org (Postfix) with ESMTPS id A40C62DC321
	for <linux-kernel@vger.kernel.org>; Mon, 25 May 2026 21:31:28 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18
ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116;
	t=1779744689; cv=none; b=YT0Lir3mmJ0T8Awhp8aDYVxcBNpU2kMSQ38bMqjkw1jmFyR9Nt/ZcpEtYONWomZgZ94jYuRO6Qb2OTL1y2quLC9JEo1Oq8aNZIPGTMZJFShOEvrogpF3fJIo88VtVZ1+sgWHcD1u0Jqr1xvizp7wtvqrx6809MnwUz9Zvus5HH8=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1779744689; c=relaxed/simple;
	bh=+7aC03be4zN4tt/LSSg6wLCcqT5Lyxa8EFFQd2DtEeY=;
	h=Date:From:To:Cc:Subject:Message-Id:In-Reply-To:References:
	 Mime-Version:Content-Type; b=HDn4sEowgS4QDA1kwyyafn1N4pvvKY+0dtv+Ww1fO+6iJLpiLqnswWU4YeH0GnAK3QvoAMr9Gp2+9QBVDob13hRJ2jvDW0TgeUSQLoRRJaACfnAhSxS4rwfp7cJe87TVzxWHzPitWQFLsInz8zZcD1a2fDooiJRaZLamyKStpxs=
ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b=fLZTMUYJ; arc=none smtp.client-ip=100.103.45.18
Authentication-Results: smtp.subspace.kernel.org;
	dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b="fLZTMUYJ"
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 148191F000E9;
	Mon, 25 May 2026 21:31:28 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=linux-foundation.org; s=korg; t=1779744688;
	bh=waL9qdEIRr0p6BZbXVVpZtKihSWhyIz/3lvf1fgmL+M=;
	h=Date:From:To:Cc:Subject:In-Reply-To:References;
	b=fLZTMUYJMH09ycEyPeoNgMuc0Rh0s7ijAW5+G+0cgZCYDVhKlawXK0eBjqOvTJX2U
	 i/hYHRO5Oigah1iY3vwGOIi6GPW2BxVYaKAholNgvcNd1absnAA1Q75So35Xb3u6Nh
	 Z24+vPjZT4fGLIPp50yOeA9Qe5IDq9AaPL1+CyIY=
Date: Mon, 25 May 2026 14:31:27 -0700
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
Message-Id: <20260525143127.9f8ff15e31df71bdb494ab61@linux-foundation.org>
In-Reply-To: <20260525044639.1888561-1-senozhatsky@chromium.org>
References: <20260525044639.1888561-1-senozhatsky@chromium.org>
X-Mailer: Sylpheed 3.8.0beta1 (GTK+ 2.24.33; x86_64-pc-linux-gnu)
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

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.