From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by smtp.lore.kernel.org (Postfix) with ESMTP id E8C1DC77B7C
	for <linux-kernel@archiver.kernel.org>; Fri,  5 May 2023 19:14:10 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S233073AbjEETOJ (ORCPT <rfc822;linux-kernel@archiver.kernel.org>);
        Fri, 5 May 2023 15:14:09 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45862 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S232979AbjEETOE (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 5 May 2023 15:14:04 -0400
Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7D5198A65
        for <linux-kernel@vger.kernel.org>; Fri,  5 May 2023 12:14:03 -0700 (PDT)
Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140])
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
        (No client certificate requested)
        by dfw.source.kernel.org (Postfix) with ESMTPS id 18A22612ED
        for <linux-kernel@vger.kernel.org>; Fri,  5 May 2023 19:14:03 +0000 (UTC)
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 16A1CC433EF;
        Fri,  5 May 2023 19:14:02 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org;
        s=korg; t=1683314042;
        bh=4jYgePMhwPc9Dims/nrzw+Gr6MqL3fFrp9uR0NeldDU=;
        h=Date:From:To:Cc:Subject:In-Reply-To:References:From;
        b=GiVZFooZFKlm2eBJ0yl4stLGsdbaO2zL2nrnRdvEQs9gHL01jH8OQ6UAtGJgJwO9D
         7tomHzm2P1nqxq4MS9PnfoFA9HbaCA+yeRynxD1pBTVwhekwj2TaStxdJ/mBFDqvRe
         VVsf7Eo5rFMN7rZwmoUdOwmQp8npdCzWp+hKnARg=
Date:   Fri, 5 May 2023 12:14:01 -0700
From:   Andrew Morton <akpm@linux-foundation.org>
To:     Nhat Pham <nphamcs@gmail.com>
Cc:     hannes@cmpxchg.org, linux-mm@kvack.org,
        linux-kernel@vger.kernel.org, minchan@kernel.org,
        ngupta@vflare.org, senozhatsky@chromium.org, sjenning@redhat.com,
        ddstreet@ieee.org, vitaly.wool@konsulko.com, kernel-team@meta.com
Subject: Re: [PATCH] zsmalloc: move LRU update from zs_map_object() to
 zs_malloc()
Message-Id: <20230505121401.31826e1251fb8792fe64f675@linux-foundation.org>
In-Reply-To: <20230505185054.2417128-1-nphamcs@gmail.com>
References: <20230505185054.2417128-1-nphamcs@gmail.com>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri,  5 May 2023 11:50:54 -0700 Nhat Pham <nphamcs@gmail.com> wrote:

> Under memory pressure, we sometimes observe the following crash:
> 
> [ 5694.832838] ------------[ cut here ]------------
> [ 5694.842093] list_del corruption, ffff888014b6a448->next is LIST_POISON1 (dead000000000100)
> 
> ...
> 
> Suggested-by: Johannes Weiner <hannes@cmpxchg.org>
> Acked-by: Johannes Weiner <hannes@cmpxchg.org>
> Signed-off-by: Nhat Pham <nphamcs@gmail.com>

Am I correct in believing that we should backport this fix into earlier
kernels?

And that a suitable Fixes: target is 64f768c6b32e ("zsmalloc: add a LRU
to zs_pool to keep track of zspages in LRU order)"?