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]

Date:	Tue, 22 May 2007 17:06:24 -0700
From:	Greg KH <greg@...ah.com>
To:	Dave Jones <davej@...hat.com>, Jeff Garzik <jeff@...zik.org>,
	jcm@...masters.org, 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 06:56:40PM -0400, Dave Jones wrote:
> On Tue, May 22, 2007 at 03:17:18PM -0700, Greg Kroah-Hartman wrote:
> 
>  > >  > >  I haven't found a single distro that (a) makes it trivial to add PCI IDs at 
>  > >  > >  install time, and then (b) ensures those PCI IDs remain persistent for each 
>  > >  > >  boot.  We are not at all to the "just works" stage yet.
>  > >  > 
>  > >  > Well, SuSE handles this just fine, but I do notice that RHEL 5 disables
>  > >  > the new_id stuff entirely, so I can see why you might get this
>  > >  > impression :)
>  > > 
>  > > That's news to me.  I didn't even realise it was possible to disable this.
>  > > Pointer?
>  > 
>  > Jon Masters told me this last week at FreedomHEC, so I don't have a
>  > pointer to the patch that disables it, sorry.
> 
> Either there's some miscommunication, or bonghits.
> 
> (18:54:00:davej@...k:kernel-2.6.18)$ kdiff vanilla/drivers/pci/pci-driver.c linux-2.6.18.noarch/drivers/pci/pci-driver.c 
> (18:54:10:davej@...k:kernel-2.6.18)$ 
> 
> And as there's no CONFIG option other than CONFIG_HOTPLUG (which we obviously enable)
> I don't see any reason why this wouldn't be enabled in RHEL5.
> (And I think mdomsch would have probably had a fit if he found out we were
>  disabling it, but that's another story ;-)

I thought so too, which is why I was so surprised when Jon said it.

Jon, is this really true, or was it the symptom of the 3rd pot of coffee
you were on that day?  :)

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/