Prev: [129/200] xen: avoid allocation causing potential swap activity on the resume path
Next: [093/200] clean DCACHE_CANT_MOUNT in d_delete()
From: Greg KH on 1 Jul 2010 17:50
2.6.34-stable review patch. If anyone has any objections, please let me know.

------------------

From: Sebastien Dugue <sebastien.dugue(a)bull.net>

commit c0dc72bad9cf21071f5e4005de46f7c8b67a138a upstream.

If the number of sg entries in the ICM chunk reaches MLX4_ICM_CHUNK_LEN,
we must set chunk to NULL even for coherent mappings so that the next
time through the loop will allocate another chunk. Otherwise we'll
overflow the sg list the next time through the loop. This will lead to
memory corruption if this case is hit.

mthca does not have this bug.

Signed-off-by: Sebastien Dugue <sebastien.dugue(a)bull.net>
Signed-off-by: Roland Dreier <rolandd(a)cisco.com>
Signed-off-by: Greg Kroah-Hartman <gregkh(a)suse.de>

---
drivers/net/mlx4/icm.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

--- a/drivers/net/mlx4/icm.c
+++ b/drivers/net/mlx4/icm.c
@@ -175,9 +175,10 @@ struct mlx4_icm *mlx4_alloc_icm(struct m

if (chunk->nsg <= 0)
goto fail;
+ }

+ if (chunk->npages == MLX4_ICM_CHUNK_LEN)
chunk = NULL;
- }

npages -= 1 << cur_order;
} else {


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [129/200] xen: avoid allocation causing potential swap activity on the resume path
Next: [093/200] clean DCACHE_CANT_MOUNT in d_delete()