This is a note to let you know that I've just added the patch titled
drm/radeon: forever loop on error in radeon_do_test_moves()
to the 3.11-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
drm-radeon-forever-loop-on-error-in-radeon_do_test_moves.patch
and it can be found in the queue-3.11 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 89cd67b326fa95872cc2b4524cd807128db6071d Mon Sep 17 00:00:00 2001
From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Date: Mon, 1 Jul 2013 19:39:34 +0300
Subject: drm/radeon: forever loop on error in radeon_do_test_moves()
From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
commit 89cd67b326fa95872cc2b4524cd807128db6071d upstream.
The error path does this:
for (--i; i >= 0; --i) {
which is a forever loop because "i" is unsigned.
Signed-off-by: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Signed-off-by: Alex Deucher <alexander.deucher@xxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/gpu/drm/radeon/radeon_test.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/drivers/gpu/drm/radeon/radeon_test.c
+++ b/drivers/gpu/drm/radeon/radeon_test.c
@@ -36,8 +36,8 @@ static void radeon_do_test_moves(struct
struct radeon_bo *vram_obj = NULL;
struct radeon_bo **gtt_obj = NULL;
uint64_t gtt_addr, vram_addr;
- unsigned i, n, size;
- int r, ring;
+ unsigned n, size;
+ int i, r, ring;
switch (flag) {
case RADEON_TEST_COPY_DMA:
Patches currently in stable-queue which might be from dan.carpenter@xxxxxxxxxx are
queue-3.11/drm-radeon-forever-loop-on-error-in-radeon_do_test_moves.patch
queue-3.11/drm-radeon-dpm-off-by-one-in-si_set_mc_special_registers.patch
queue-3.11/watchdog-ts72xx_wdt-locking-bug-in-ioctl.patch
queue-3.11/drm-radeon-dpm-btc-off-by-one-in-btc_set_mc_special_registers.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html