Received: by 2002:a4a:301c:0:0:0:0:0 with SMTP id q28-v6csp595561oof; Tue, 25 Sep 2018 01:59:34 -0700 (PDT) X-Google-Smtp-Source: ACcGV60ngptNJ1hYLqFOAGchlVZBPGXm5iHM+HkCrxvm7sFVgr1LO6d23/a9td0b5LTsnyhoPdzk X-Received: by 2002:a62:920d:: with SMTP id o13-v6mr2564556pfd.177.1537865973948; Tue, 25 Sep 2018 01:59:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537865973; cv=none; d=google.com; s=arc-20160816; b=z/r74AML1L+S6/cPACWZsENb0Cu7+gKPfSh8nNVkg9yMMCOAnOc8KyQZWO+3UMQWkI 8u5sPG+71Tb3/WqAzin66Xk0WDMgJi7BhE/+kXolGkbYAtYriqtn8t6qiBOA+tBWQrs+ mJgya7xQUJ4Z4vnNv5Pr9/u+6mJiNbhnP0OC5SvHKfgLqst2eoDMkkyILIzbR4BTzEwS yDhWzREUy+ipnbj4CsECCBi12+UJzMo5aKffjba/HDehTzXSC0QpxUOpHCf1e1QlLkux DFGCQatCVYyLsq1oFAmTJz3Coi6EWvkA/krAnwjwEgL49uhMwFo3E6+epVElvuHsLO9C MSIA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=jO5YFRnUbuuxuHIKfrPgz/xY6vXX0j9P7XP99gfFDX8=; b=uH56Y6UCN0piAblRkHGSGDbJ/49ckxtrnz4k+/S28AuTZuXl1BIkhYpRYRhSiP0gN3 L/LjbTPUCrXv0kf4KqPQlcW7q38Q85HSQzTjs4mj9t5S08M5LrKYKW2qKwBfCehmf+jD H1mMapbMcVWifX1doTW+VI9Y8QX1dItnX5NrWBgET08xTd8D1/mDj+cFWV7Gd53yI+Fr 4CAMrAA3rgmW03fOvbpw4SM86jsxA8SqwkpN97yNvRLwpc9tci6j97vRM6VrJPZ5Zzi6 3ARugM6ybZw1dDWxBWsJMjbWqMUF5b6R/YU2WoVMIAQOgKu8gS8MQFPXD2Hxyiu0k9fc ammw== ARC-Authentication-Results: i=1; mx.google.com; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d27-v6si1860691pgd.223.2018.09.25.01.59.19; Tue, 25 Sep 2018 01:59:33 -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; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728619AbeIYPFX (ORCPT + 99 others); Tue, 25 Sep 2018 11:05:23 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58166 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726660AbeIYPFW (ORCPT ); Tue, 25 Sep 2018 11:05:22 -0400 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 10AE830842D0; Tue, 25 Sep 2018 08:58:52 +0000 (UTC) Received: from localhost (ovpn-8-17.pek2.redhat.com [10.72.8.17]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 6EFBB1001914; Tue, 25 Sep 2018 08:58:49 +0000 (UTC) Date: Tue, 25 Sep 2018 16:58:46 +0800 From: Baoquan He To: Bjorn Helgaas Cc: Lianbo Jiang , Vivek Goyal , linux-kernel@vger.kernel.org, kexec@lists.infradead.org, tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, x86@kernel.org, akpm@linux-foundation.org, dan.j.williams@intel.com, thomas.lendacky@amd.com, baiyaowei@cmss.chinamobile.com, tiwai@suse.de, bp@suse.de, brijesh.singh@amd.com, dyoung@redhat.com Subject: Re: [PATCH 3/3] resource: Fix find_next_iomem_res() iteration issue Message-ID: <20180925085846.GY2555@MiWiFi-R3L-srv> References: <153782698067.130337.12079523922130875402.stgit@bhelgaas-glaptop.roam.corp.google.com> <153782730364.130337.17794279728329113665.stgit@bhelgaas-glaptop.roam.corp.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <153782730364.130337.17794279728329113665.stgit@bhelgaas-glaptop.roam.corp.google.com> User-Agent: Mutt/1.9.1 (2017-09-22) X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.40]); Tue, 25 Sep 2018 08:58:52 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Bjorn, On 09/24/18 at 05:15pm, Bjorn Helgaas wrote: > @@ -359,32 +362,31 @@ static int find_next_iomem_res(struct resource *res, unsigned long desc, > read_unlock(&resource_lock); > if (!p) > return -1; > + > /* copy data */ > - if (res->start < p->start) > - res->start = p->start; > - if (res->end > p->end) > - res->end = p->end; > + res->start = max(start, p->start); > + res->end = min(end, p->end); > res->flags = p->flags; I think this fix is good. However, is it OK to keep res->flags always, never touch it in find_next_iomem_res()? We just iterate and update region, its start and end. So just removing that "res->flags = p->flags;" line might involve much less code changes. Thanks Baoquan