Re: [linux-usb-devel] [RFC] g_serial: Real tty device passthrough.

2007-03-09 Thread Harald Welte
rial device emulation' of g_serial, and then spliced with the physical serial device. > Maybe you'll need some other work for this to work fine... I'll be > reading Samsung's s3c2410 serial code to check how to connect them... There is nothing specific to th

Re: [linux-usb-devel] Large control write transfers / zero-length-packet at end

2006-09-20 Thread Harald Welte
On Wed, Sep 20, 2006 at 06:28:15PM -0700, David Brownell wrote: > On Wednesday 20 September 2006 10:58 am, Harald Welte wrote: > > > > When a control-out transfer takes, the host controller sends a SETUP > > > packet followed by as many OUT/DATA packets as necessary to

Re: [linux-usb-devel] Large control write transfers / zero-length-packet at end

2006-09-20 Thread Harald Welte
dication. Seems to work just fine now. I spent already more than one day at this problem ;( Thanks once again. Cheers, -- - Harald Welte <[EMAIL PROTECTED]> http://gnumonks.org/ We all know

[linux-usb-devel] Large control write transfers / zero-length-packet at end

2006-09-20 Thread Harald Welte
LP at the end of the transfer, or is this all done by the host controller? Any other ideas? -- - Harald Welte <[EMAIL PROTECTED]> http://gnumonks.org/ We all know Linux is great...it does infinite lo

[linux-usb-devel] Re: [PATCH] Make usbdevice_fs.h (again) useable from userspace

2005-11-14 Thread Harald Welte
On Mon, Nov 14, 2005 at 06:45:27PM +0100, Arjan van de Ven wrote: > On Mon, 2005-11-14 at 18:37 +0100, Harald Welte wrote: > > Make usbdevice_fs.h (again) useable from userspace > > > > If we have CONFIG_COMPAT enabled, then userspace programs using > > usbdevice

[linux-usb-devel] [PATCH] Make usbdevice_fs.h (again) useable from userspace

2005-11-14 Thread Harald Welte
Make usbdevice_fs.h (again) useable from userspace If we have CONFIG_COMPAT enabled, then userspace programs using usbdevice_fs.h won't compile anymore. Signed-off-by: Harald Welte <[EMAIL PROTECTED]> --- commit 17c6b20f34d9d68918346af2a2eb6433b0

[linux-usb-devel] Re: [vendor-sec] Re: [BUG/PATCH/RFC] Oops while completing async USB via usbdevio

2005-10-12 Thread Harald Welte
t I'll do the incremental patch + testing tonight. So I expect some kind of reply on this at about 11pm (GMT+1). Sorry once again for the delays, but as I said initially: I'm neither a core kernel / scheduler nor a USB developer. If somebody else had taken the bug, we'd have had

Re: [linux-usb-devel] Re: [BUG/PATCH/RFC] Oops while completing async USB via usbdevio

2005-10-11 Thread Harald Welte
On Mon, Oct 10, 2005 at 04:03:13PM -0400, Alan Stern wrote: > On Mon, 10 Oct 2005, Harald Welte wrote: > > > + if ((!info || ((unsigned long)info != 1 && > > + (unsigned long)info != 2 && SI_FROMUSER(info))) > > +

[linux-usb-devel] Re: [BUG/PATCH/RFC] Oops while completing async USB via usbdevio

2005-10-11 Thread Harald Welte
On Mon, Oct 10, 2005 at 11:07:45AM -0700, Chris Wright wrote: > * Harald Welte ([EMAIL PROTECTED]) wrote: > > diff --git a/kernel/signal.c b/kernel/signal.c > > --- a/kernel/signal.c > > +++ b/kernel/signal.c > > @@ -1193,6 +1193,40 @@ kill_proc_info(int sig, struct sig

[linux-usb-devel] Re: [BUG/PATCH/RFC] Oops while completing async USB via usbdevio

2005-10-10 Thread Harald Welte
On Fri, Sep 30, 2005 at 03:16:28PM -0700, Linus Torvalds wrote: > > > On Sat, 1 Oct 2005, Harald Welte wrote: > > > > please find the patch below. It compiles, but I didn't yet have the > > time to verify it makes the bug disappear and the async urb delivery is

Re: [linux-usb-devel] Re: [Security] [vendor-sec] [BUG/PATCH/RFC] Oops while completing async USB via usbdevio

2005-10-02 Thread Harald Welte
current->euid); /* * The null signal is a permissions and process existence * probe. No signal is actually delivered. @@ -2330,7 +2365,8 @@ sys_tkill(int pid, int sig) p = find_task_by_pid(pid); error = -ESRCH;

Re: [linux-usb-devel] Re: [Security] [vendor-sec] [BUG/PATCH/RFC] Oops while completing async USB via usbdevio

2005-09-30 Thread Harald Welte
inus' suggested "PID approach" yet, I'd be willing to write a patch and test it. Please let me know. Please also understand that I never argued that my initial patch was a good solution, or that I wanted it to have merged. I just wanted to show that there is a r

[linux-usb-devel] [BUG/PATCH/RFC] Oops while completing async USB via usbdevio

2005-09-25 Thread Harald Welte
e delivered signal. c) Q: If this is a local DoS, why did you post it publicly? A: Because I've already informed linux-usb-devel in May. I suggest this (or any other) fix to be applied to both 2.6.14 final and the stable series. I didn't yet investigate 2.4.x, but I think it is like

Re: [linux-usb-devel] Re: [BUG] oops while completing async USB via usbdevio

2005-06-06 Thread Harald Welte
would > > have to walk that task_list and check which tasks have opened this file. > > What about something like the standard FSETOWN fnctl? I investigated this option, too. The magic behind FSETOWN doesn't allow us to pass the URB address back to the process (toget

Re: [linux-usb-devel] Re: [BUG] oops while completing async USB via usbdevio

2005-06-06 Thread Harald Welte
On Wed, Jun 01, 2005 at 12:12:58AM +0200, Harald Welte wrote: > > > Wouldn't it help to associate the URB with the file (instaed of the > > > task), and then send the signal to any task that still has opened the > > > file? I'm willing to hack up a pa

Re: [linux-usb-devel] Re: [BUG] oops while completing async USB via usbdevio

2005-05-31 Thread Harald Welte
out already exists, > so the main missing piece is that urb-to-file binding. Ok, I'll get something coded shortly. -- - Harald Welte <[EMAIL PROTECTED]> http://gnumonks.org/ "Privacy

Re: [linux-usb-devel] Re: [BUG] oops while completing async USB via usbdevio

2005-05-31 Thread Harald Welte
It seems to me that the whole usbdevio async handling doesn't really cope with a lot of the unix semantics, such as fork() or file descriptor passing. Wouldn't it help to associate the URB with the file (instaed of the task), and then send the signal to any task that still has opened the fi

[linux-usb-devel] Re: [BUG] oops while completing async USB via usbdevio

2005-05-31 Thread Harald Welte
termination, we do a linear search over the global list of pending URB's and terminate those where urb->task == taks_to_kill? Sounds a bit expensive, especially since you don't know (before iteration) whether that task has actually ever dealt with usbdevio

Re: [linux-usb-devel] Re: [BUG] oops while completing async USB via usbdevio

2005-05-31 Thread Harald Welte
gt; complete.  So the pointer to the task "should" be valid for as long as > > any URB it's submitted is active. > > What happens if you pass such an fd through a socket? which is exactly what happens on certain distributions for all device opens if you look at SuSE's r

[linux-usb-devel] Re: [BUG] oops while completing async USB via usbdevio

2005-05-30 Thread Harald Welte
On Mon, May 30, 2005 at 09:44:44PM +0200, Harald Welte wrote: > I think there is currently no protection/locking/refcounting going on. > > If a process issues an URB from userspace and starts to terminate before > the URB comes back, we run into the issue described above. This is &

[linux-usb-devel] [BUG] oops while completing async USB via usbdevio

2005-05-30 Thread Harald Welte
the scheduler code to decide what fix is the way to go. Is it sufficient to do {get,put}_task_struct() from the usb code? Any comments welcome... -- - Harald Welte <[EMAIL PROTECTED]> http://gnumonks.org/ ===

[linux-usb-devel] mmap() for usbdevfs, zerocopy EHCI ?

2005-05-01 Thread Harald Welte
he usb subsystem. Do you think a system described above is actually feasible? If yes, what kind of implementation suggestions do you have? [1] http://comsec.com/wiki [2] http://comsec.com/wiki?UniversalSoftwareRadioPeripheral -- - Harald Welte <[EMAIL PROTECTED]>

[linux-usb-devel] [PATCH 2.6] maintainers / documentation update cyberjack

2005-02-14 Thread Harald Welte
Here's a pure documentation update for the cyberjack driver. Please apply at your convenience, thanks. -- - Harald Welte <[EMAIL PROTECTED]> http://www.hmw-consulting.de/ = Consultant for linux networki

[linux-usb-devel] Re: USBmon

2004-12-16 Thread Harald Welte
't actually need any userland, you can just cat the contents of the respective files. It's ascii output. > Thanks, > -- Pete -- - Harald Welte <[EMAIL PROTECTED]> http://www.gnumonks.org/ ===

Re: [linux-usb-devel] usbfs2 ... what should be in it?

2004-06-16 Thread Harald Welte
On Wed, Jun 16, 2004 at 11:14:51AM -0700, Johannes Erdfelt wrote: > Take for example the reset device call. How would that map into a > sockets interface? maybe setsockopt? > JE -- - Harald Welte <[EMAIL PROTECTED]> http://w

Re: [linux-usb-devel] [PATCH] USB fixes for 2.6.7-rc3

2004-06-16 Thread Harald Welte
s not good. Exactly what sequence of steps did you do to > achive it? [host controller driver: uhci_hcd] - plug in the device, have the driver hotplug-loaded - start 'cjgeldkarte' - have 'cjgeldkarte' terminate - unplug the device > thanks, > greg k-h -- - Harald

Re: [linux-usb-devel] [PATCH] USB fixes for 2.6.7-rc3

2004-06-16 Thread Harald Welte
On Wed, Jun 16, 2004 at 11:17:10AM +0200, Harald Welte wrote: > Apparently interface->dev is 0x10 here, thus usb_get_drvdata() inlined by > get_intfdata() dereferences 0x10+0x74 == 0x84 After some more debugging, it becomes obvious that usb_serial_disconnect() is called twic

Re: [linux-usb-devel] usbfs2 ... what should be in it?

2004-06-16 Thread Harald Welte
g is very analogous to what tcpdump [or other pcap based software] dpes. The socket level could then determine whether you're intereted in sniffing/sending raw usb packets at the HCD (RAW usb socket) or whether you're interested in communicating with a specific device/interface

Re: [linux-usb-devel] [PATCH] USB fixes for 2.6.7-rc3

2004-06-16 Thread Harald Welte
jne1e70 Apparently interface->dev is 0x10 here, thus usb_get_drvdata() inlined by get_intfdata() dereferences 0x10+0x74 == 0x84 Any ideas? -- - Harald Welte <[EMAIL PROTECTED]> http://www.gnumonks.org/

Re: [linux-usb-devel] USBMon for kernel 2.4.20

2004-06-04 Thread Harald Welte
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Jun 04, 2004 at 09:54:46AM -0700, Greg KH wrote: > On Fri, Jun 04, 2004 at 06:07:49PM +0200, Harald Welte wrote: > > yes, I dislike it, too. But as I'm not the original author and just > > touched somebody else's code

Re: [linux-usb-devel] USBMon for kernel 2.4.20

2004-06-04 Thread Harald Welte
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Jun 04, 2004 at 07:45:48AM -0700, Pete Zaitcev wrote: > On Fri, 4 Jun 2004 16:23:19 +0200 > Harald Welte <[EMAIL PROTECTED]> wrote: > > > + dev = (struct usb_device *)(file->private_data); > > + >

[linux-usb-devel] USBMon for kernel 2.4.20

2004-06-04 Thread Harald Welte
I'll port/merge USBMon for 2.4.26 and 2.6.6 during the next week, too. -- - Harald Welte <[EMAIL PROTECTED]> http://www.gnumonks.org/ Programming is like sex: One mistake and you have to support