On Thu, 8 Apr 2010, Hendrik Sattler wrote: > It was a problem with my obex server application. However, that should never > cause a total freeze. Running through valgrind somehow made it survive the > bug. I wrong pointer was given to the write() call, probably with invalid > memory. A quick lock at gs_write() in u_serial.c didn't show any checks that > the buffer pointer is valid. Is this already done by the tty layer itself? Since the pointer passed to gs_write() points to a kernelspace buffer rather than a userspace buffer, the check must have been made somewhere else. Maybe in the tty layer, maybe even in the VFS layer. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
