linux-kernel - Re: [PATCH] Driver core: add new device to bus's list before probing

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] [day] [month] [year] [list]

Message-ID: <20090731164159.GA25624@kroah.com>
Date:	Fri, 31 Jul 2009 09:41:59 -0700
From:	Greg KH <greg@...ah.com>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Driver core: add new device to bus's list before
 probing

On Fri, Jul 31, 2009 at 12:30:03PM -0400, Kay Sievers wrote:
> On Fri, Jul 31, 2009 at 12:05, Greg KH<greg@...ah.com> wrote:
> > On Thu, Jul 30, 2009 at 04:57:06PM -0400, Kay Sievers wrote:
> >> On Thu, Jul 30, 2009 at 15:27, Alan Stern<stern@...land.harvard.edu> wrote:
> 
> >> > Kay, do you want this merged into 2.6.31 or are you okay with waiting
> >> > for 2.6.32-rc1?  It changes a major core routine.  On the other hand,
> >> > the problem it fixes does affect real users.
> >>
> >> I think it should go into -next and we wait a few days. It seems like
> >> the proper fix, but we should make sure, we didn't miss something.
> >>
> >> After that, it would be nice if we can get that into 2.6.31, as we
> >> have several problems already, which are likely solved by this.
> >
> > But as this isn't a regression (it's how things always have worked,
> > right?),
> 
> Yeah, that sounds right, but I guess we have just been the needed bit
> slower in the past, and with the recent speedups I would expect more
> cases to uncover this issue.
> 
> > I'm a bit leary of pushing it to .31 right now, so late in the
> > release cycle.  How about it goes to Linus for .32, and we backport it
> > to -stable if it looks ok?
> 
> Sure, sounds fine too.
> 
> Would be good though to have it in -next soon. Three major distros are
> preparing a new distro release at the moment, and they will likely
> need to add that to their kernel to make this issue, USB firmware
> loading, and similar things working again.

It will show up in the next linux-next release.

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/