linux-kernel - Re: [PATCH 0/1] Recurse when searching for empty slots in resources trees

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: <alpine.LFD.2.01.0906171309500.16802@localhost.localdomain>
Date:	Wed, 17 Jun 2009 13:12:42 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Andrew Patterson <andrew.patterson@...com>
cc:	Matthew Wilcox <matthew@....cx>,
	Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>,
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	jbarnes@...tuousgeek.org
Subject: Re: [PATCH 0/1] Recurse when searching for empty slots in resources
 trees



On Wed, 17 Jun 2009, Andrew Patterson wrote:
> > 
> > This is why I'd really like to see the output of my test-patch. It would 
> > show exactly _where_ that resource is inserted, and the whole call-chain.
> > 
> > I'm appending a version that only does it for resources that have names 
> > starting with "PCI Bus", so it should be less noisy. But again, it's 
> > totally untested.
> > 
> 
> Here you go (I can provide the full boot log if needed). Note, there is
> nothing for c3 here:

Ok, so that means it got inserted into the resource tree some other way 
entirely. Or maybe the name got changed after-the-fact. Both of which 
imply that something is really really wrong.

The ones your trace _does_ show are the ones that got inserted correctly 
and aren't buggy. Can anybody see how that buggy resource got inserted?

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