linux-kernel - Re: Regression with commit f9cde5f in 2.6.30-gitX

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:	Wed, 24 Jun 2009 14:24:24 -0700
From:	Gary Hade <garyhade@...ibm.com>
To:	Larry Finger <Larry.Finger@...inger.net>
Cc:	Gary Hade <garyhade@...ibm.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Jaswinder Singh Rajput <jaswinder@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	x86 maintainers <x86@...nel.org>, Len Brown <lenb@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Regression with commit f9cde5f in 2.6.30-gitX

On Wed, Jun 24, 2009 at 03:05:12PM -0500, Larry Finger wrote:
> Gary Hade wrote:
> > On Wed, Jun 24, 2009 at 08:45:31PM +0200, Thomas Gleixner wrote:
> >> Can we just bring the limit check back and increase the number for now
> >> until folks come up with a better solution ?
> > 
> > Another possible option is leaving in the limit check (still valid
> > IMO for correct behavior of previous 'pci=use_crs') and reverting
> >  http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=9e9f46c44e487af0a82eb61b624553e2f7118f5b
> > until the better solution for the fixed size array issue is
> > available.
> 
> Either increasing PCI_BUS_NUM_RESOURCES from 16 to 20 or 24

Yes, it looks to me like 20 might be the absolute minimum
that your system could tolerate.  The big mystery is how much
to increase it so we don't see the same problem on other
systems where _CRS may return some unknown amount more that
the 17 resources that are being returned on your system.

> or reverting f9cde5f will work for my system.

This would not be good without also reverting
9e9f46c44e487af0a82eb61b624553e2f7118f5b since devices
below the transparent bridge on your's and other's systems
may have trouble getting the resources they need.

Removing the check would only hide possibly more insidious
and difficult to debug problems that could show up later.
This was the main reason I provided the patch.  This kind
of check should have actually existed prior to
9e9f46c44e487af0a82eb61b624553e2f7118f5b when 'pci=use_crs'
was needed to enable use of the _CRS data.

Thanks,
Gary

-- 
Gary Hade
System x Enablement
IBM Linux Technology Center
503-578-4503  IBM T/L: 775-4503
garyhade@...ibm.com
http://www.ibm.com/linux/ltc

--
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/