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]
Date:	Tue, 22 May 2007 12:36:45 -0700
From:	Greg KH <greg@...ah.com>
To:	Dave Jones <davej@...hat.com>, Chuck Ebbert <cebbert@...hat.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Chris Wright <chrisw@...s-sol.org>
Subject: Re: [stable] Wanted: Allow adding new device IDs during the
	-stable cycle

On Tue, May 22, 2007 at 02:53:53PM -0400, Dave Jones wrote:
> On Tue, May 22, 2007 at 11:47:33AM -0700, Greg Kroah-Hartman wrote:
>  > On Tue, May 22, 2007 at 02:14:44PM -0400, Chuck Ebbert wrote:
>  > > I'd like to propose we allow adding new device IDs as part
>  > > of the -stable process, but only under certain conditions:
>  > 
>  > Who would be the primary benifactor of this?
>  > 
>  > The very large majority of users out there use a distro kernel, and they
>  > provide the ids whenever possible as patches to their kernels, _or_ as a
>  > config option at startup that adds the ids to the drivers through sysfs.
> 
> It does mean however that there's lots of duplicated work between
> distros as everyone adds these patches anyway.

But distros don't all standardize on the same -stable release anyway, so
I don't see how a large ammount of duplicated work happens here.

>  > What's wrong with the current sysfs way of adding new device ids without
>  > touching the kernel?
> 
> sure, that works in some cases, but for others (quirks etc) it obviously doesn't.

I totally agree, and have never objected to quirk additions in the past.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ