Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1406729pxb; Mon, 22 Feb 2021 00:34:41 -0800 (PST) X-Google-Smtp-Source: ABdhPJx0cujxgi6an2XZiNUOH/Lc8i2f5AtenX31n6b/ysGUN0H3Sei4MD9JiEHCPOxyXztmgm40 X-Received: by 2002:a05:6402:946:: with SMTP id h6mr8468221edz.188.1613982881480; Mon, 22 Feb 2021 00:34:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1613982881; cv=none; d=google.com; s=arc-20160816; b=OggLlaB1aXQ54dj/fZCx2RLeDo6BNK55WEYTW4KJJwXWzd5V50foEBScI4XmgDAZYj akZcTGwGEinjiAPtc4Ip2PxAk1KPHt3ekCTwtVPjL+niif12KBY318sRA40cdokbQAFS zkLJt4YhY4fMdpqYE/4vHWKNtSseLBP4rRsCCW09E9iiNnph47dMMh/762O0yPyHBhve RReRcY0w+uhsJfM3HCaBc9Jb3mxQW3pcdN+h1tbTUBdZFDVykyoFo+sOOTJtdcMU8d6c feyGytBVmqamNdvNNZwd5HpcWBVB9tEportn+hL5dvRDUVRW4wy3o0pKvYm+j6SSmxFQ Qwcg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=zmWkGYIaCCw8mtQmi1p4MTfm8qVfNgEdPbexW0q29RI=; b=b5MvZZ0Ico5OiMtf63Gv53EWdhMTtJeSKdPCbwQkSzEsITfNzHoKmcCp0wv8QgixIm iHCQ4ciNfy5ltmgyxJOJS2X1QCg75OVH3v0zhoY7m3vTP6mu11dcWIXQHN22WffhzTuz OrzUoWau1C4hB3IvlL+XMkkO/i/mzHKdW7oLF6S4F6BOd80KmcnuAEf4aIyEHsSC8mD8 pi8KajPbrRR4VDZ6+q2/EnLZal3xw8+XFskQcIeAfCNDU+8lLFd1eM2no3PYd34FtWck 8efdi4GiCs0xxtrtgr12qPvrd9aKgScSqIuQ7zMADP9rRjtEp1UiuDKuWf9lZ2iBlaxH //hw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.com header.s=susede1 header.b=tnEsNhyR; 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=QUARANTINE sp=NONE dis=NONE) header.from=suse.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w26si1454874ejf.489.2021.02.22.00.34.18; Mon, 22 Feb 2021 00:34:41 -0800 (PST) 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=@suse.com header.s=susede1 header.b=tnEsNhyR; 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=QUARANTINE sp=NONE dis=NONE) header.from=suse.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230008AbhBVIbV (ORCPT + 99 others); Mon, 22 Feb 2021 03:31:21 -0500 Received: from mx2.suse.de ([195.135.220.15]:33944 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229967AbhBVIbU (ORCPT ); Mon, 22 Feb 2021 03:31:20 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1613982633; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=zmWkGYIaCCw8mtQmi1p4MTfm8qVfNgEdPbexW0q29RI=; b=tnEsNhyRIjzJkTMRqIuFVbxRwqFGqW2Ix9CuVlIeg9mhaTDSqcB3pLKarLARUPu24SmjKn 1PYw2Bc7YKtKNy/rPni/YyBYrJsCxtDaP9H8QXWewiqA531v4pV6MyXBJOlSEtTqT+qf4B RfTLKj3qXLYIWsFyWSpiOXecE0yiYwE= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 6D0AAAD73; Mon, 22 Feb 2021 08:30:33 +0000 (UTC) Date: Mon, 22 Feb 2021 09:30:27 +0100 From: Michal Hocko To: "Matthew Wilcox (Oracle)" Cc: linux-mm@kvack.org, Andrew Morton , linux-kernel@vger.kernel.org Subject: Re: [PATCH] mm: Use rcu_dereference in in_vfork Message-ID: References: <20210221194207.1351703-1-willy@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210221194207.1351703-1-willy@infradead.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun 21-02-21 19:42:06, Matthew Wilcox wrote: > Fix a sparse warning by using rcu_dereference(). Technically this is a > bug and a sufficiently aggressive compiler could reload the `real_parent' > pointer outside the protection of the rcu lock (and access freed memory), > but I think it's pretty unlikely to happen. > > Fixes: b18dc5f291c0 ("mm, oom: skip vforked tasks from being selected") > Signed-off-by: Matthew Wilcox (Oracle) I must have missed the RCU part. Thanks! Acked-by: Michal Hocko > --- > include/linux/sched/mm.h | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/include/linux/sched/mm.h b/include/linux/sched/mm.h > index 1ae08b8462a4..90b2a0bce11c 100644 > --- a/include/linux/sched/mm.h > +++ b/include/linux/sched/mm.h > @@ -140,7 +140,8 @@ static inline bool in_vfork(struct task_struct *tsk) > * another oom-unkillable task does this it should blame itself. > */ > rcu_read_lock(); > - ret = tsk->vfork_done && tsk->real_parent->mm == tsk->mm; > + ret = tsk->vfork_done && > + rcu_dereference(tsk->real_parent)->mm == tsk->mm; > rcu_read_unlock(); > > return ret; > -- > 2.29.2 > -- Michal Hocko SUSE Labs