From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Bob Picco <bpicco@redhat.com>,
Brian Bloniarz <phunge0@hotmail.com>,
Charles Butterfield <charles.butterfield@nextcentury.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
linux-pci@vger.kernel.org,
"Horst H. von Brand" <vonbrand@inf.utfsm.cl>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Stefan Becker <chemobejk@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>, Yinghai Lu <yinghai@kernel.org>,
Leann Ogasawara <leann.ogasawara@canonical.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH v4 1/6] resources: ensure alignment callback doesn't allocate below available start
Date: Thu, 14 Oct 2010 17:18:26 -0600 [thread overview]
Message-ID: <20101014231826.536.51757.stgit@bob.kio> (raw)
In-Reply-To: <20101014231804.536.62138.stgit@bob.kio>
The alignment callback returns a proposed location, which may have been
adjusted to avoid ISA aliases or for other architecture-specific reasons.
We already had a check ("tmp.start < tmp.end") to make sure the callback
doesn't return a location above the available area.
This patch adds a check to make sure the callback doesn't return something
*below* the available area, as may happen if the callback tries to allocate
top-down.
Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
---
kernel/resource.c | 10 ++++++++--
1 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/kernel/resource.c b/kernel/resource.c
index 7b36976..ace2269 100644
--- a/kernel/resource.c
+++ b/kernel/resource.c
@@ -371,6 +371,7 @@ static int find_resource(struct resource *root, struct resource *new,
{
struct resource *this = root->child;
struct resource tmp = *new;
+ resource_size_t start;
tmp.start = root->start;
/*
@@ -391,8 +392,13 @@ static int find_resource(struct resource *root, struct resource *new,
if (tmp.end > max)
tmp.end = max;
tmp.start = ALIGN(tmp.start, align);
- if (alignf)
- tmp.start = alignf(alignf_data, &tmp, size, align);
+ if (alignf) {
+ start = alignf(alignf_data, &tmp, size, align);
+ if (tmp.start <= start && start <= tmp.end)
+ tmp.start = start;
+ else
+ tmp.start = tmp.end;
+ }
if (tmp.start < tmp.end && tmp.end - tmp.start >= size - 1) {
new->start = tmp.start;
new->end = tmp.start + size - 1;
next prev parent reply other threads:[~2010-10-14 23:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 23:18 [PATCH v4 0/6] PCI: allocate space top-down, not bottom-up Bjorn Helgaas
2010-10-14 23:18 ` Bjorn Helgaas [this message]
2010-10-14 23:18 ` [PATCH v4 2/6] resources: support allocating space within a region from the top down Bjorn Helgaas
2010-10-14 23:18 ` [PATCH v4 3/6] PCI: allocate bus resources " Bjorn Helgaas
2010-10-14 23:18 ` [PATCH v4 4/6] x86/PCI: allocate space from the end of a region, not the beginning Bjorn Helgaas
2010-10-14 23:18 ` [PATCH v4 5/6] x86: update iomem_resource end based on CPU physical address capabilities Bjorn Helgaas
2010-10-14 23:18 ` [PATCH v4 6/6] x86: allocate space within a region top-down Bjorn Helgaas
2010-10-25 21:01 ` Jesse Barnes
2010-10-25 21:08 ` Bjorn Helgaas
2010-10-25 21:15 ` Bjorn Helgaas
2010-10-25 21:17 ` Jesse Barnes
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=20101014231826.536.51757.stgit@bob.kio \
--to=bjorn.helgaas@hp.com \
--cc=bpicco@redhat.com \
--cc=charles.butterfield@nextcentury.com \
--cc=chemobejk@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=phunge0@hotmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vonbrand@inf.utfsm.cl \
--cc=yinghai@kernel.org \
/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