Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp2733754pxv; Mon, 12 Jul 2021 00:11:53 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxG8FO6x04C1T4hpXjN7A44TchUOMCMkPSZ5U/hjDcuBeZw7Zh8oM1dpWT2GUjPft+Z+IcQ X-Received: by 2002:a02:c851:: with SMTP id r17mr42414314jao.13.1626073821503; Mon, 12 Jul 2021 00:10:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626073821; cv=none; d=google.com; s=arc-20160816; b=RRpq/8Zu1hhg5Fyzc/0PHrpGwGurdVZrdB89EYstnr96mmwT1NSxCVOXO2zc52eTUo 8WY6JPmjBZwISMqgNboifv/5VGYVPnld4Y5X69g9NwKthbvjevHwaFNQq+24m+6zcPxz aNFqHAXBY/hwYOfxgbpI5nhmwDkRDbyjo7t51xRKJ+syfYNznrDQvf0DroHkF+MSK0Ho 3o7H4+LCfJt2vXkaiqvw1U5El7fmHEQ/rFjhC+F0Aua4X0+WO2s5pYpsUkuPs7RJYeUn TcrgOosnRgsZrYrNxGbQOAfGZoXlCCvyHmpPLNYdMu8CXCB6GtkNfbwrO3VCoZST/i/7 cKPw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=AjLLm2+Lmk3tutwoSnY1eo1VQUU+39YtXxUHJL2191M=; b=AFJdInQXkcOZfp21uPrndFyOgA3e8Kbu+yh9bIc135wXV0D7Y7OTr1ruelwlTNjf/r LavYCP/KkdVPJ651lCn4B2KdWhQQ7853ptRJAk0a3d2HeNVLxghH/GSSMAiiUBytsTCG kEFRPUFGdNHOY+CdEch1b5gMbMN5gDKD5K0G9iXxUoIdGez08QOzUOOJOaXF8+wiJpxd 6En95r94YDGrJUt3AcnNrK22VlqjGknCnAu4PW1e2cmYBOvO7NW0zF7D46DN15YjTdNC 99fZMsTUoz6OWHHzEqNDxYnYbWO2WwBMULbKE8u59rBrYxYnEQRTtum1afBPhPWCYR6b DSdw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b="2m/moxa+"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n10si17806378ilk.143.2021.07.12.00.10.09; Mon, 12 Jul 2021 00:10:21 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b="2m/moxa+"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244528AbhGLHK4 (ORCPT + 99 others); Mon, 12 Jul 2021 03:10:56 -0400 Received: from mail.kernel.org ([198.145.29.99]:45554 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238630AbhGLGs7 (ORCPT ); Mon, 12 Jul 2021 02:48:59 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 740D061151; Mon, 12 Jul 2021 06:44:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1626072273; bh=c+FtSA1C+MkBqKGS90RHSaVnYBX/7KJM9eYZJGGEP+Q=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=2m/moxa+685IImuefzSBH1DLsOOSpvA5k9RQl3jHXjLQmS0YFck1mGH6uSJN10+zy PV/4mXuf2Y5TF/4lN4H/qEHtc7hvh1iV1C5J2vaPNgJHXQSXREJsG1BGyV4+0Blibd /W2zFRztWoQMMWiux6BtRnQ8SmNxCZLyOk47uOPg= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Muchun Song , Michal Hocko , Tejun Heo , Jan Kara , Sasha Levin Subject: [PATCH 5.10 426/593] writeback: fix obtain a reference to a freeing memcg css Date: Mon, 12 Jul 2021 08:09:46 +0200 Message-Id: <20210712060935.244487699@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210712060843.180606720@linuxfoundation.org> References: <20210712060843.180606720@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Muchun Song [ Upstream commit 8b0ed8443ae6458786580d36b7d5f8125535c5d4 ] The caller of wb_get_create() should pin the memcg, because wb_get_create() relies on this guarantee. The rcu read lock only can guarantee that the memcg css returned by css_from_id() cannot be released, but the reference of the memcg can be zero. rcu_read_lock() memcg_css = css_from_id() wb_get_create(memcg_css) cgwb_create(memcg_css) // css_get can change the ref counter from 0 back to 1 css_get(memcg_css) rcu_read_unlock() Fix it by holding a reference to the css before calling wb_get_create(). This is not a problem I encountered in the real world. Just the result of a code review. Fixes: 682aa8e1a6a1 ("writeback: implement unlocked_inode_to_wb transaction and use it for stat updates") Link: https://lore.kernel.org/r/20210402091145.80635-1-songmuchun@bytedance.com Signed-off-by: Muchun Song Acked-by: Michal Hocko Acked-by: Tejun Heo Signed-off-by: Jan Kara Signed-off-by: Sasha Levin --- fs/fs-writeback.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c index afda7a7263b7..a0869194ab73 100644 --- a/fs/fs-writeback.c +++ b/fs/fs-writeback.c @@ -510,9 +510,14 @@ static void inode_switch_wbs(struct inode *inode, int new_wb_id) /* find and pin the new wb */ rcu_read_lock(); memcg_css = css_from_id(new_wb_id, &memory_cgrp_subsys); - if (memcg_css) - isw->new_wb = wb_get_create(bdi, memcg_css, GFP_ATOMIC); + if (memcg_css && !css_tryget(memcg_css)) + memcg_css = NULL; rcu_read_unlock(); + if (!memcg_css) + goto out_free; + + isw->new_wb = wb_get_create(bdi, memcg_css, GFP_ATOMIC); + css_put(memcg_css); if (!isw->new_wb) goto out_free; -- 2.30.2