| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20090828191714.GI10360@sequoia.sous-sol.org>
Date: Fri, 28 Aug 2009 12:17:14 -0700
From: Chris Wright <chrisw@...s-sol.org>
To: Jesse Barnes <jbarnes@...tuousgeek.org>,
Ivan Kokshaysky <ink@...assic.park.msu.ru>
Cc: Matthew Wilcox <matthew@....cx>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Yu Zhao <yu.zhao@...el.com>, linux-kernel@...r.kernel.org,
linux-pci@...r.kernel.org, stable@...nel.org
Subject: [PATCH] SR-IOV: correct broken resource alignment calculations
An SR-IOV capable device includes an SR-IOV PCIe capability which
describes the Virtual Function (VF) BAR requirements. A typical SR-IOV
device can support multiple VFs whose BARs must be in a contiguous region,
effectively an array of VF BARs. The BAR reports the size requirement
for a single VF. We calculate the full range needed by simply multiplying
the VF BAR size with the number of possible VFs and create a resource
spanning the full range.
This all seems sane enough except it artificially inflates the alignment
requirement for the VF BAR. The VF BAR need only be aligned to the size
of a single BAR not the contiguous range of VF BARs. This can cause us
to fail to allocate resources for the BAR despite the fact that we
actually have enough space.
This patch adds a support for a new resource alignment type,
IORESOURCE_VSIZEALIGN, and allows struct resource to keep track of the
size requirements of a VF BAR which are smaller than the full resource
size. This could also be done all within the PCI layer w/out bloating
struct resource or using the last available bit for alignment types.
Comments?
Signed-off-by: Chris Wright <chrisw@...s-sol.org>
Cc: Jesse Barnes <jbarnes@...tuousgeek.org>
Cc: Ivan Kokshaysky <ink@...assic.park.msu.ru>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Matthew Wilcox <matthew@....cx>
Cc: Yu Zhao <yu.zhao@...el.com>
Cc: stable@...nel.org
---
drivers/pci/iov.c | 12 +++++++++++-
include/linux/ioport.h | 6 ++++++
kernel/resource.c | 7 ++++++-
3 files changed, 23 insertions(+), 2 deletions(-)
diff --git a/drivers/pci/iov.c b/drivers/pci/iov.c
index e3a8721..c860dc6 100644
--- a/drivers/pci/iov.c
+++ b/drivers/pci/iov.c
@@ -101,7 +101,9 @@ static int virtfn_add(struct pci_dev *dev, int id, int reset)
if (!res->parent)
continue;
virtfn->resource[i].name = pci_name(virtfn);
- virtfn->resource[i].flags = res->flags;
+ /* single VF BAR with normal size/alignment */
+ virtfn->resource[i].flags = res->flags & ~IORESOURCE_VSIZEALIGN;
+ virtfn->resource[i].flags |= IORESOURCE_SIZEALIGN;
size = resource_size(res);
do_div(size, iov->total);
virtfn->resource[i].start = res->start + size * id;
@@ -468,6 +470,14 @@ found:
rc = -EIO;
goto failed;
}
+ /*
+ * VF BAR need only be aligned to size of single BAR, not
+ * whole contiguous range. So keep vsize available for
+ * alignment queries.
+ */
+ res->flags &= ~IORESOURCE_SIZEALIGN;
+ res->flags |= IORESOURCE_VSIZEALIGN;
+ res->vend = res->end;
res->end = res->start + resource_size(res) * total - 1;
nres++;
}
diff --git a/include/linux/ioport.h b/include/linux/ioport.h
index 786e7b8..cd30c66 100644
--- a/include/linux/ioport.h
+++ b/include/linux/ioport.h
@@ -18,6 +18,7 @@
struct resource {
resource_size_t start;
resource_size_t end;
+ resource_size_t vend;
const char *name;
unsigned long flags;
struct resource *parent, *sibling, *child;
@@ -48,6 +49,7 @@ struct resource_list {
#define IORESOURCE_SIZEALIGN 0x00020000 /* size indicates alignment */
#define IORESOURCE_STARTALIGN 0x00040000 /* start field is alignment */
+#define IORESOURCE_VSIZEALIGN 0x00080000 /* vsize indicates alignment */
#define IORESOURCE_MEM_64 0x00100000
@@ -130,6 +132,10 @@ static inline resource_size_t resource_size(struct resource *res)
{
return res->end - res->start + 1;
}
+static inline resource_size_t resource_vsize(struct resource *res)
+{
+ return res->vend - res->start + 1;
+}
static inline unsigned long resource_type(struct resource *res)
{
return res->flags & IORESOURCE_TYPE_BITS;
diff --git a/kernel/resource.c b/kernel/resource.c
index 78b0872..6e24295 100644
--- a/kernel/resource.c
+++ b/kernel/resource.c
@@ -569,11 +569,16 @@ EXPORT_SYMBOL(adjust_resource);
*/
resource_size_t resource_alignment(struct resource *res)
{
- switch (res->flags & (IORESOURCE_SIZEALIGN | IORESOURCE_STARTALIGN)) {
+ unsigned long mask = (IORESOURCE_SIZEALIGN |
+ IORESOURCE_STARTALIGN |
+ IORESOURCE_VSIZEALIGN);
+ switch (res->flags & mask) {
case IORESOURCE_SIZEALIGN:
return resource_size(res);
case IORESOURCE_STARTALIGN:
return res->start;
+ case IORESOURCE_VSIZEALIGN:
+ return resource_vsize(res);
default:
return 0;
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists