From: Ram Pai <linuxram@us.ibm.com>
To: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
weiyang@linux.vnet.ibm.com, wangyun@linux.vnet.ibm.com,
shangw@linux.vnet.ibm.com, Michal Ludvig <mludvig@logix.net.nz>
Subject: [PATCH] Resource: wrong resource window calculation
Date: Thu, 22 Sep 2011 15:48:58 +0800 [thread overview]
Message-ID: <20110922074858.GG5085@ram-ThinkPad-T61> (raw)
In-Reply-To: <4E6F400A.6090909@logix.net.nz>
Resource: wrong resource window calculation
__find_resource() incorrectly returns a resource window which overlaps an
existing allocated window. This happens when the parent's resource-window spans
0x00000000 to 0xffffffff and is entirely allocated to all its children
resource-windows.
__find_resource() looks for gaps in resource allocation among the children
resource windows. When it encounters the last child window it blindly tries
the range next to one allocated to the last child. Since the last child's
window ends at 0xffffffff the calculation overflows, leading the algorithm to
believe that any window in the range 0x0000000 to 0xfffffff is available for
allocation. This leads to a conflicting window allocation.
Michal Ludvig reported this issue seen on his platform. The following patch
fixes the problem and has been verified by Michal. I believe this bug has been
there for ages. It got exposed by git commit
2bbc6942273b5b3097bd265d82227bdd84b351b2
[PATCH] PCI : ability to relocate assigned pci-resources
Signed-off-by: Ram Pai <linuxram@us.ibm.com>
---
kernel/resource.c | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/kernel/resource.c b/kernel/resource.c
index 3ff4017..b29b83d 100644
--- a/kernel/resource.c
+++ b/kernel/resource.c
@@ -419,6 +419,9 @@ static int __find_resource(struct resource *root, struct resource *old,
else
tmp.end = root->end;
+ if (tmp.end < tmp.start)
+ goto next;
+
resource_clip(&tmp, constraint->min, constraint->max);
arch_remove_reservations(&tmp);
@@ -436,8 +439,10 @@ static int __find_resource(struct resource *root, struct resource *old,
return 0;
}
}
- if (!this)
+
+next: if (!this || this->end == root->end)
break;
+
if (this != old)
tmp.start = this->end + 1;
this = this->sibling;
--
1.7.4.1
next parent reply other threads:[~2011-09-22 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E5E0A7E.40301@logix.net.nz>
[not found] ` <CAErSpo70k6UnhvvOMgQQxJ6BHZOwym=-jaPMvOukAaCr-B0+cQ@mail.gmail.com>
[not found] ` <4E5EFFBD.4050201@logix.net.nz>
[not found] ` <CAErSpo6bofeiAxeRo_RjXQSnwmcWrdymn0MK8H4_CwqwoeD1jg@mail.gmail.com>
[not found] ` <4E634814.4050508@logix.net.nz>
[not found] ` <20110909113409.GE2416@ram-ThinkPad-T61>
[not found] ` <4E6C05B7.9000904@logix.net.nz>
[not found] ` <20110913110646.GB2425@ram-ThinkPad-T61>
[not found] ` <4E6F400A.6090909@logix.net.nz>
2011-09-22 7:48 ` Ram Pai [this message]
2011-09-22 9:50 ` [PATCH] Resource: wrong resource window calculation Michal Ludvig
2011-09-28 15:42 ` Ram Pai
2011-09-30 2:44 ` Linus Torvalds
2011-09-30 2:56 ` Michal Ludvig
2011-09-30 2:59 ` Ram Pai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110922074858.GG5085@ram-ThinkPad-T61 \
--to=linuxram@us.ibm.com \
--cc=bhelgaas@google.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mludvig@logix.net.nz \
--cc=shangw@linux.vnet.ibm.com \
--cc=wangyun@linux.vnet.ibm.com \
--cc=weiyang@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox