linux-kernel - Re: [stable] to something appropriate (was Re: 2.6.22 -mm merge plans)

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 for Android: free password hash cracker in your pocket

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

Message-ID: <46376748.6020408@redhat.com>
Date:	Tue, 01 May 2007 12:14:00 -0400
From:	Chuck Ebbert <cebbert@...hat.com>
To:	Greg KH <greg@...ah.com>
CC:	Jeff Garzik <jeff@...zik.org>, Chris Wright <chrisw@...s-sol.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, stable@...nel.org
Subject: Re: [stable] to something appropriate (was Re: 2.6.22 -mm merge	plans)

Greg KH wrote:
> On Mon, Apr 30, 2007 at 08:45:25PM -0400, Jeff Garzik wrote:
>> Chris Wright wrote:
>>> 2) you can add them
>>> runtime in userspace (and for pcmcia too after patch in question is
>>> applied), so we've historically avoided that kind of patch for -stable.
>>
>> Due to distro installer environments, and very poor support for making 
>> dynamic PCI IDs persistent once added, what you describe is more of a 
>> goal than reality.
> 
> But distros can easily add the device id to their kernel if needed, it
> isn't something that the -stable tree shoud be accepting.  Otherwise, we
> will be swamped with those types of patches...
> 

Oh sure, leave the distros swamped with them instead. :)

And they all have to do it separately, meaning they don't stay in sync
and they duplicate each other's work...

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