Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp3294862ybi; Mon, 17 Jun 2019 21:26:43 -0700 (PDT) X-Google-Smtp-Source: APXvYqwFnQKlyLwT3PFEsfE0bhKp8L3aNO3mDT62deov3Smlm9vKzHGeQ+AwX+3AVKTlQB1smC9v X-Received: by 2002:a62:ce07:: with SMTP id y7mr2138625pfg.12.1560832003285; Mon, 17 Jun 2019 21:26:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560832003; cv=none; d=google.com; s=arc-20160816; b=QD4+RqIQw2nzaVklQmxNwFLex9G83xdr/dQNLu+/XqhEKNQ0bzzpOoPPWr/wLywE1r 5rKv/T63W+In4zmiBGBiYXtoF/mPjWzHtXQWcR9ic7H04oB1CINfyrWFyU5tk0LUGRlW fMHWI2jYHwFZcajHtV6wEhKLxXK0QIHBuu9nJ9dZRpEkGfvKawG8qYEGzdnwyiOLoKcH mfGLPWKXhNdd8W3TEN86GvB1yPilOB8APwu8qFcrpRsOIfz4kFK5LxeVKuWIyq2Qat4Z 6WcJWfwJI0deh4x3l0HnowcaD8ibzZ4c4/OkezeLurKkgDIf0nhWq3KeEy27XNHySAfM kdGA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=L4HcxDuuNAoD4D5yeHroWYczHTL+R16auCPmQfIRMQY=; b=k+Z5ZjCAC444HEmemMWg7qEAXKNxglD9gJ1PtVN0X6uGvrkxNYUmi3yQpYIG4DOjQA gQGS5NkmTEnnWIioqP8rvbAAFg1GcHqCUOE9cIW5m8ZhWOCi5WPDhvE2vSFINffGAZYv VsL6jTq7/n0jklc2VM+Fk0gxhfMkCeBIO35po5iKS9ouBE9+7+IofgXEOW6dR2fmEXYG HM9QziQkNqxlzjiYBOkqJgCIvGGtNW4FcRA3KyZNmeE39JhpJS5aEFM/OtPVRgpaU+3k CqqBPlxR6njRgJKNfGs7UN35t2yeuRqTJtogOqCEpyunmqgxhcfVWF79PDWVDscLCrcv AtCw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=R6ur39y7; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l7si2639782plb.8.2019.06.17.21.26.27; Mon, 17 Jun 2019 21:26:43 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=R6ur39y7; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726576AbfFRE0I (ORCPT + 99 others); Tue, 18 Jun 2019 00:26:08 -0400 Received: from mail.kernel.org ([198.145.29.99]:59846 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725883AbfFRE0I (ORCPT ); Tue, 18 Jun 2019 00:26:08 -0400 Received: from localhost.localdomain (c-73-223-200-170.hsd1.ca.comcast.net [73.223.200.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 854072084D; Tue, 18 Jun 2019 04:26:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1560831967; bh=xv/fCdFQ6SfbaJzNr+4Vp5gITAmLP6lf4CXGPgHSad8=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=R6ur39y7TUbCZ9I9GPNBpsgEq0A7kXynJU20VbzOQGtqant4HGaLMKo1/Qfhk7cr7 tde33KHi5Y7TxhTaqqC6+HziktP/p9+akYAS8ke5AZ3GOrAwOuR0iaD1yngtP6A7Zt xKHocsz345eJckm197hPRlWYwLgBSR8v5C1arUzU= Date: Mon, 17 Jun 2019 21:26:05 -0700 From: Andrew Morton To: Nadav Amit Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, stable@vger.kernel.org, Borislav Petkov , Toshi Kani , Peter Zijlstra , Dave Hansen , Dan Williams , Bjorn Helgaas , Ingo Molnar Subject: Re: [PATCH 1/3] resource: Fix locking in find_next_iomem_res() Message-Id: <20190617212605.bb8cc4571ee67879033e1bc4@linux-foundation.org> In-Reply-To: <20190613045903.4922-2-namit@vmware.com> References: <20190613045903.4922-1-namit@vmware.com> <20190613045903.4922-2-namit@vmware.com> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 12 Jun 2019 21:59:01 -0700 Nadav Amit wrote: > Since resources can be removed, locking should ensure that the resource > is not removed while accessing it. However, find_next_iomem_res() does > not hold the lock while copying the data of the resource. Looks right to me. > Keep holding the lock while the data is copied. While at it, change the > return value to a more informative value. It is disregarded by the > callers. The kerneldoc needs a resync: --- a/kernel/resource.c~resource-fix-locking-in-find_next_iomem_res-fix +++ a/kernel/resource.c @@ -326,7 +326,7 @@ EXPORT_SYMBOL(release_resource); * * If a resource is found, returns 0 and @*res is overwritten with the part * of the resource that's within [@start..@end]; if none is found, returns - * -1 or -EINVAL for other invalid parameters. + * -ENODEV. Returns -EINVAL for invalid parameters. * * This function walks the whole tree and not just first level children * unless @first_lvl is true. _