Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp14712527rwb; Mon, 28 Nov 2022 04:18:01 -0800 (PST) X-Google-Smtp-Source: AA0mqf7C6xoBKtOhhYX7SD+usjT6PwuBQDXYqUlo0iYUEOPq1tVVWc1mLjCtIs0T7wchLa957n4Q X-Received: by 2002:a17:906:fa19:b0:78d:9002:fe3b with SMTP id lo25-20020a170906fa1900b0078d9002fe3bmr39418288ejb.769.1669637881652; Mon, 28 Nov 2022 04:18:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669637881; cv=none; d=google.com; s=arc-20160816; b=gDJAzec+JVLEH38qvLhA/T0mLouaYm1kZVELg+MHkB71e50XM0Pd0047fwxB0dWDBB ogrw6uORPOepXwkGmw4jzIebV+8FXylp407lmJqGPsWSV+MY1JuKiYpUVIybH6H7BCWI E46HEpCOMTotYnCWCNN/xFX+5rqMEWnM15VcugQgNOVPoBMMfunmM+yNjzcl1I7gpllI AFZuj9A/UT2tXzp/dzwMds0dxTXVEiCGCRC4GWrMbs4DR02H2yEz+NGVHfYxImBNxq2g QdcXnpJDstsdwNcJ4VpzTqy/XYAhbe//OS1uj5KVz9cLwGhT8YGA0JP0hfnuNmwqgG7e mFhg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=pvDk61od7nv4vDF5T7ZQlBxH29nUJtkQ4YMcnkcS/cA=; b=aT7UIl1hrGO+NHVzDcMAJKKYp2JRkzstKutRjg1ZAPAf5DH0hBuzMB1hgQ1IG++PB8 uIWeQ3N5ZmFX7jdD7IAEhmBEvLPjdtCsgma8KGvip1LbeRH3vj+1I0btSas18IvSNhUG Jx11SVrLrnb0ki1r1bVNAe7QoY61vrEqYZDcBw2aSrFAtTwlxz/FUU7+q0VFxBf/HriG 0tqO9gQpM39hLo0D/fgUhcrLoxCCa9GnHdzXhaAx4SdOqn9ndW2gwR165kmU7h4/kG9S XD2oeGZbWxNTcaEaTaB56nHYV0mFScAZgL5i+EHpcRhL4dnB00TXa6HxoVT8Jkyj443O x42A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=rAoJRYGi; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id z12-20020a056402274c00b0046afd9f07b0si5065261edd.14.2022.11.28.04.17.40; Mon, 28 Nov 2022 04:18:01 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=rAoJRYGi; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231572AbiK1MCd (ORCPT + 84 others); Mon, 28 Nov 2022 07:02:33 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36312 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229890AbiK1MAU (ORCPT ); Mon, 28 Nov 2022 07:00:20 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1DD8C18B27 for ; Mon, 28 Nov 2022 04:00:19 -0800 (PST) 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 ams.source.kernel.org (Postfix) with ESMTPS id BDF8AB80D88 for ; Mon, 28 Nov 2022 12:00:17 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D8A11C4315C; Mon, 28 Nov 2022 12:00:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1669636816; bh=s8HTQY8UHN5dZej09qiZkVk+0Pf068ApxSd4spgbW8I=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=rAoJRYGiK+WR4soWiM4j+Tjgu3098aU+PNHTqh+UuFslYHjkymkBUlCd0Rck6uTu7 kh/1Vt9xJMvoJ0XygbUBxXDLo60kzRTfB29c+ALWBe1d05Hb276Hsi6zesun6jm/KO rV/ldVtrp8FoqRGP0IGUguF6mTj8kGfvgXWlQegSjUa/VdA00TzQ5Ugss2/9hddAba RtXUcU3yewbt5Z0ADdwJrg6vA87yra/jHBuOULXzxxnf2p6YE5MnUmSRt1ajM6RlId Np7x2qp2jthQ0aB0iUfrn3h9PdYBVlmF9urfrIwmcgVY7V83JJ5k/aECGpL9y63QO9 Q3+7nQyrgnOVw== Date: Mon, 28 Nov 2022 12:00:10 +0000 From: Will Deacon To: Waiman Long Cc: Ingo Molnar , Peter Zijlstra , Juri Lelli , Vincent Guittot , Dietmar Eggemann , Steven Rostedt , Ben Segall , Mel Gorman , Daniel Bristot de Oliveira , Phil Auld , Wenjie Li , David Wang =?utf-8?B?546L5qCH?= , linux-kernel@vger.kernel.org Subject: Re: [PATCH-tip v4] sched: Fix NULL user_cpus_ptr check in dup_user_cpus_ptr() Message-ID: <20221128120008.GA25090@willie-the-truck> References: <20221125023943.1118603-1-longman@redhat.com> <92b99a5e-1588-4e08-a652-72e9c51421cf@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <92b99a5e-1588-4e08-a652-72e9c51421cf@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Nov 27, 2022 at 08:43:27PM -0500, Waiman Long wrote: > On 11/24/22 21:39, Waiman Long wrote: > > In general, a non-null user_cpus_ptr will remain set until the task dies. > > A possible exception to this is the fact that do_set_cpus_allowed() > > will clear a non-null user_cpus_ptr. To allow this possible racing > > condition, we need to check for NULL user_cpus_ptr under the pi_lock > > before duping the user mask. > > > > Fixes: 851a723e45d1 ("sched: Always clear user_cpus_ptr in do_set_cpus_allowed()") > > Signed-off-by: Waiman Long > > This is actually a pre-existing use-after-free bug since commit 07ec77a1d4e8 > ("sched: Allow task CPU affinity to be restricted on asymmetric systems"). > So it needs to be fixed in the stable release as well. Will resend the patch > with an additional fixes tag and updated commit log. Please can you elaborate on the use-after-free here? Looking at 07ec77a1d4e8, the mask is only freed in free_task() when the usage refcount has dropped to zero and I can't see how that can race with fork(). What am I missing? Will > > kernel/sched/core.c | 32 ++++++++++++++++++++++++++++---- > > 1 file changed, 28 insertions(+), 4 deletions(-) > > > > [v4] Minor comment update > > > > diff --git a/kernel/sched/core.c b/kernel/sched/core.c > > index 8df51b08bb38..f2b75faaf71a 100644 > > --- a/kernel/sched/core.c > > +++ b/kernel/sched/core.c > > @@ -2624,19 +2624,43 @@ void do_set_cpus_allowed(struct task_struct *p, const struct cpumask *new_mask) > > int dup_user_cpus_ptr(struct task_struct *dst, struct task_struct *src, > > int node) > > { > > + cpumask_t *user_mask; > > unsigned long flags; > > + /* > > + * Always clear dst->user_cpus_ptr first as their user_cpus_ptr's > > + * may differ by now due to racing. > > + */ > > + dst->user_cpus_ptr = NULL; > > + > > + /* > > + * This check is racy and losing the race is a valid situation. > > + * It is not worth the extra overhead of taking the pi_lock on > > + * every fork/clone. > > + */ > > if (!src->user_cpus_ptr) > > return 0; > > - dst->user_cpus_ptr = kmalloc_node(cpumask_size(), GFP_KERNEL, node); > > - if (!dst->user_cpus_ptr) > > + user_mask = kmalloc_node(cpumask_size(), GFP_KERNEL, node); > > + if (!user_mask) > > return -ENOMEM; > > - /* Use pi_lock to protect content of user_cpus_ptr */ > > + /* > > + * Use pi_lock to protect content of user_cpus_ptr > > + * > > + * Though unlikely, user_cpus_ptr can be reset to NULL by a concurrent > > + * do_set_cpus_allowed(). > > + */ > > raw_spin_lock_irqsave(&src->pi_lock, flags); > > - cpumask_copy(dst->user_cpus_ptr, src->user_cpus_ptr); > > + if (src->user_cpus_ptr) { > > + swap(dst->user_cpus_ptr, user_mask); > > + cpumask_copy(dst->user_cpus_ptr, src->user_cpus_ptr); > > + } > > raw_spin_unlock_irqrestore(&src->pi_lock, flags); > > + > > + if (unlikely(user_mask)) > > + kfree(user_mask); > > + > > return 0; > > } >