linux-kernel - Re: linux-next: Tree for April 10: generic pci_enable

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:	Sun, 13 Apr 2008 21:28:47 -0700
From:	Greg KH <greg@...ah.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Mariusz Kozlowski <m.kozlowski@...land.pl>,
	David Miller <davem@...emloft.net>
Subject: Re: linux-next: Tree for April 10: generic pci_enable_resources()
	strikes again

On Mon, Apr 14, 2008 at 11:48:23AM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> On Thu, 10 Apr 2008 21:34:00 +0200 Mariusz Kozlowski <m.kozlowski@...land.pl> wrote:
> >
> > 	The commit b818da52 makes my sparc64 box simply unable to boot.
> > You should probably take a look at other arches as well. The story is here:
> > 
> > http://lkml.org/lkml/2008/3/28/465
> > http://lkml.org/lkml/2008/4/1/248
> 
> This patch has remained unchanged since first imported into linux-next in
> March 6.
> 
> So, the question is: What are the consequences of reverting it?  I am not
> in a position to judge, but if it causes boxes to simply not boot, then
> it would be a major regression in 2.6.26 and simply cannot be included
> there.
> 
> I will revert it at the end of today's tree and hope that there is some
> resolution before the merge window opens.
> 
> Of course, there is still the question of the other architectures ...

Yes, I haven't caught up with my emails, but yes, this will not go
upstream for those arches that have had problems with it (like sparc64).
I'll fix my tree up first thing Monday morning for this issue.

Sorry for taking so long with it, been stuck doing other things...

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/