linux-kernel - Re: [linux-usb-devel] [GIT PATCH] USB fixes for 2.6.20-rc5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070122202344.GA10579@suse.de>
Date:	Mon, 22 Jan 2007 12:23:44 -0800
From:	Greg KH <gregkh@...e.de>
To:	Marcel Holtmann <marcel@...tmann.org>
Cc:	Linus Torvalds <torvalds@...l.org>, Andrew Morton <akpm@...l.org>,
	linux-kernel@...r.kernel.org, linux-usb-devel@...ts.sourceforge.net
Subject: Re: [linux-usb-devel] [GIT PATCH] USB fixes for 2.6.20-rc5

On Mon, Jan 22, 2007 at 09:15:04PM +0100, Marcel Holtmann wrote:
> Hi Greg,
> 
> > They include a small number of fixes for some USB bugs, and some new
> > device ids, all of the details are below.  I've also disabled the USB
> > multithreaded probe option, as it broke a number of people's machines.
> 
> what about the two pending patches to make device_move() working as
> expected. The current implementation is broken and basically useless.

I don't feel comfortable adding them to the 2.6.20 kernel at this late
period, for a variety of reasons.  I really want them to be tested out
in the -mm tree and then in the full -rc series due to the fact that
they are non-trivial, and touch the driver core code that everyone uses,
not just that function.

Also, it's a new feature (reparent back to the original parent), not
necessarily a bugfix.

And yes, I realize that the functions don't work fully right now, but as
long as you don't want to re-parent the devices, they should work,
right?

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/