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: <20070522184733.GA9357@kroah.com>
Date:	Tue, 22 May 2007 11:47:33 -0700
From:	Greg KH <greg@...ah.com>
To:	Chuck Ebbert <cebbert@...hat.com>
Cc:	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: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.

> 1) Each device (or group of devices) gets added as a separate
>    patch, i.e. we don't just diff the device tables. This way
>    each original patch that added the device(s) upstream will
>    be become a single patch for -stable.
> 
> 2) Devices that require new features/capabilities in their
>    driver won't be added.

What's wrong with the current sysfs way of adding new device ids without
touching the kernel?  Devices described above was the very reason we
added that functionality, so users would not have to constantly update
their kernel.  The distros provide userspace tools that enable these ids
to be added and at boot time, everything "just works" properly.

So, because of that, I don't really see a need to be adding new device
ids to the -stable tree.

> Candidate patches would be something like these, which together
> add support for the ATI SB700 ATA controller:
> 
> 1)
> http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=823777181b4c0200923dcb026efa5b37f55c0ecf
> 
> Adds ATI sb700 quirk, using exactly the same one as sb600.

That's a quirk addition, not a new device id following the above
mentioned rules you set out :)

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/