linux-kernel - Re: [stable] Wanted: Allow adding new device IDs during the -stable cycle

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: <46537314.4080605@garzik.org>
Date:	Tue, 22 May 2007 18:47:48 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Chris Wright <chrisw@...s-sol.org>
CC:	Greg KH <greg@...ah.com>, Chuck Ebbert <cebbert@...hat.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [stable] Wanted: Allow adding new device IDs during the	-stable
 cycle

Chris Wright wrote:
> 2) In theory new hardware can seem to work with a simple PCI ID
> update, and later we find it needs extra quirk handling or specific
> driver support.  This could mean adding buggy support for new hardware
> to -stable.  In practice, hopefully this isn't a real issue.

No need to worry about theory.  Since you are (or should be???) taking 
stuff solely from upstream, you should already know what is needed, or not.


> 3) It hasn't been a pressing issue brought to our attention until this
> thread and its predecessor earlier in the month.

Search your email archives, it has been brought more than the two times 
you cite.


> My own personal experience is each time I've needed a PCI ID update for
> new hardware it's also needed changes to the driver (read: e1000, every
> single time).  So from my perspective neither sysfs nor relaxing -stable
> rules slightly would actually help provide support for new hardware,
> but that's clearly limited experience.

e1000 is not a representative sample at all...

	Jeff


-
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/