Skip to contentSkip to conversation

V4L bug report - oops: video_register_device (ksymoops, objdump)

PATCH Gerd Knorr 1 participant 1 message May 5, 2004 1 message not in the archive Media (V4L/DVB)

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Gerd Knorr

author
#1 lore raw
Quoted 4 lines · On Wed, May 05, 2004 at 02:20:32AM +0200, [email protected] wrote:

I caused an oops in unusual circumstances by accidentally "forcing" a video device number which was too high or already taken (don't know which). I assume this probably shouldn't give an oops (though it was my fault), so here's a bugreport...

Fixed by adding a range check for the number passed in by the driver. The fix applies to 2.4 kernels as well.

Gerd

drivers/media/video/videodev.c renamed from drivers/media/video/videodev.c~ +8 -8
@@ -316,7 +316,14 @@
 
 	/* pick a minor number */
 	down(&videodev_lock);
-	if (-1 == nr) {
+	if (nr >= 0  &&  nr < end-base) {
+		/* use the one the driver asked for */
+		i = base+nr;
+		if (NULL != video_device[i]) {
+			up(&videodev_lock);
+			return -ENFILE;
+		}
+	} else {
 		/* use first free */
 		for(i=base;i<end;i++)
 			if (NULL == video_device[i])
@@ -325,13 +332,6 @@
 			up(&videodev_lock);
 			return -ENFILE;
 		}
-	} else {
-		/* use the one the driver asked for */
-		i = base+nr;
-		if (NULL != video_device[i]) {
-			up(&videodev_lock);
-			return -ENFILE;
-		}
 	}
 	video_device[i]=vfd;
 	vfd->minor=i;