Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp3417362pxf; Mon, 29 Mar 2021 01:26:14 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx6dSx4bazo3BxMQxV+90491fmu96B0eAjl2+NB6xuymFE0g9wpb76vedAXXGy5R5wLmr5W X-Received: by 2002:a17:907:10c1:: with SMTP id rv1mr27659700ejb.5.1617006374325; Mon, 29 Mar 2021 01:26:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617006374; cv=none; d=google.com; s=arc-20160816; b=nwDkFRzKHV4ui6KZdG3sejqqc+LLJPMaYsMU6l+CYtjW8yWZATkRX4JWXIRDt6yC6e 8Ned2cUK+Hw3YutxSlxr7fUCgtCCcJW6mZcXIKroJSy213Vw63B83FBjiaR0wGYc2rHg ooUGR5JmXieNe8Q1ZAAGmIrhUbpUNfHOfmGpApRT7A4n4aXNpLU65jcbSniGMGd6M9Hq 9l8Y9Bz/B4Tubvz4RD0uMTtXPjVLk0JLMCrsUzD8wNDOG3mtks8uPNPMda7Yu13tZd/W Yj7MCYp/70Cv6vF4pDcGOPDoC3DVzAruOmZuXTKJxXMmrMS8VdQPQUxcgLB1OiJ3XQfs NPxg== 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=PTNrTbG+lIle/PJo7kK3LWqBn1qhwbwQQn7LsCR0GPE=; b=YFbaBbhWsPe4791sxOyRHvj0V7ah2h5IBzf5YKf06RRbuoYHbc0w6hZCZ6KJdNTFyq QN42sMtdzFKLyaX+qqjtOHipww2elfdwPBKgnVXUHS8XXx4bmbnF4iRoPlnsofX9qT4X 5JO1LcakDEoiec1XnSa/FWBy/8EBdcqDTY3nUweVhlgm0iF/xs62yqz2kyQLuMGQj3nG H9mZq01v3KnWQcLkz1Gn4b7J6xFcO7r7kYoDc+pIybz+SWh0tFBmmKZBkQZRAJykuDQ2 zxJk1vGe1AIT2MQr6LOJVid9DfNj2JxkOsmQf66eZGw17zPMBoJkQ4mrWvYza7VNY/bw sQBQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=hc4CGf3D; 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 e13si13182934edz.432.2021.03.29.01.25.51; Mon, 29 Mar 2021 01:26:14 -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=hc4CGf3D; 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 S233409AbhC2IZH (ORCPT + 99 others); Mon, 29 Mar 2021 04:25:07 -0400 Received: from mail.kernel.org ([198.145.29.99]:57602 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233137AbhC2IQ3 (ORCPT ); Mon, 29 Mar 2021 04:16:29 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 4D800619AD; Mon, 29 Mar 2021 08:15:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1617005754; bh=jAIgNxABpd2gmJESv1yf+CKNWvDZWkhGpVcS0+/i0XU=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=hc4CGf3DtDp4aNQQiuE9rOyfYc3zWpx1ifJOTFiZmtTCx2VhLTu//fmapvBM9ZAaV 39Xpfz9bv/KpD1VWptc04G5vkd981e/sV8v3w3UCleR8wygHx+lMF3OZWbDbO/lrY6 ElXVjEc1MaS56i9H22Gv/D4kfm3x76BQuLxC6xrk= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Thomas Gleixner , "Peter Zijlstra (Intel)" , Ingo Molnar Subject: [PATCH 5.4 104/111] locking/mutex: Fix non debug version of mutex_lock_io_nested() Date: Mon, 29 Mar 2021 09:58:52 +0200 Message-Id: <20210329075618.677000665@linuxfoundation.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20210329075615.186199980@linuxfoundation.org> References: <20210329075615.186199980@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: Thomas Gleixner commit 291da9d4a9eb3a1cb0610b7f4480f5b52b1825e7 upstream. If CONFIG_DEBUG_LOCK_ALLOC=n then mutex_lock_io_nested() maps to mutex_lock() which is clearly wrong because mutex_lock() lacks the io_schedule_prepare()/finish() invocations. Map it to mutex_lock_io(). Fixes: f21860bac05b ("locking/mutex, sched/wait: Fix the mutex_lock_io_nested() define") Signed-off-by: Thomas Gleixner Signed-off-by: Peter Zijlstra (Intel) Signed-off-by: Ingo Molnar Cc: stable@vger.kernel.org Link: https://lkml.kernel.org/r/878s6fshii.fsf@nanos.tec.linutronix.de Signed-off-by: Greg Kroah-Hartman --- include/linux/mutex.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/include/linux/mutex.h +++ b/include/linux/mutex.h @@ -171,7 +171,7 @@ extern void mutex_lock_io(struct mutex * # define mutex_lock_interruptible_nested(lock, subclass) mutex_lock_interruptible(lock) # define mutex_lock_killable_nested(lock, subclass) mutex_lock_killable(lock) # define mutex_lock_nest_lock(lock, nest_lock) mutex_lock(lock) -# define mutex_lock_io_nested(lock, subclass) mutex_lock(lock) +# define mutex_lock_io_nested(lock, subclass) mutex_lock_io(lock) #endif /*