All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: lkml <linux-kernel@vger.kernel.org>
Cc: linux-usb-users@lists.sourceforge.net,
	Greg Kroah-Hartman <greg@kroah.com>
Subject: [PATCH 2.6.5-rc2] CAN-2004-0075 still valid for 2.6?
Date: Sat, 20 Mar 2004 20:59:33 +0100	[thread overview]
Message-ID: <200403202059.33039@WOLK> (raw)

[-- Attachment #1: Type: text/plain, Size: 266 bytes --]

Hi Greg,

seems $subject is still valid for 2.6, no? - 2.4 got a fix 11 weeks ago.

See this: 
http://linux.bkbits.net:8080/linux-2.4/diffs/drivers/usb/vicam.c@1.15?nav=index.html|
src/|src/drivers|src/drivers/usb|hist/drivers/usb/vicam.c

Please apply.

ciao, Marc

[-- Attachment #2: CAN-2004-0075-usb-vicam.patch --]
[-- Type: text/x-diff, Size: 840 bytes --]

# drivers/usb/media/vicam.c |   13 ++++++++++---
# 1 files changed, 10 insertions(+), 3 deletions(-)

diff -urN linux-old/drivers/usb/media/vicam.c linux-wolk-for-2.6drivers/usb/media/vicam.c
--- linux-old/drivers/usb/media/vicam.c	2003-11-28 10:26:20.000000000 -0800
+++ linux-wolk-for-2.6drivers/usb/media/vicam.c	2004-01-15 12:10:23.000000000 -0800
@@ -653,12 +653,19 @@
 	case VIDIOCSWIN:
 		{
 
-			struct video_window *vw = (struct video_window *) arg;
-			DBG("VIDIOCSWIN %d x %d\n", vw->width, vw->height);
+			struct video_window vw;
 
-			if ( vw->width != 320 || vw->height != 240 )
+			if (copy_from_user(&vw, arg, sizeof(vw)))
+			{
 				retval = -EFAULT;
+				break;
+			}
+
+			DBG("VIDIOCSWIN %d x %d\n", vw->width, vw->height);
 			
+			if ( vw.width != 320 || vw.height != 240 )
+				retval = -EFAULT;
+
 			break;
 		}
 

             reply	other threads:[~2004-03-20 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-20 19:59 Marc-Christian Petersen [this message]
2004-03-20 20:16 ` [PATCH 2.6.5-rc2] CAN-2004-0075 still valid for 2.6? Greg KH

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=200403202059.33039@WOLK \
    --to=m.c.p@wolk-project.de \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-users@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.