linux-kernel - Re: 2.6.25-rc8-mm1 panic in rpaphp_register

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: <1208588626.6958.446.camel@pasglop>
Date:	Sat, 19 Apr 2008 17:03:46 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Alex Chiang <achiang@...com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, pbadari@...ibm.com,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.25-rc8-mm1 panic in rpaphp_register_slot()

On Sat, 2008-04-19 at 00:38 -0600, Alex Chiang wrote:
> So I'm not sure how much we can use of your slot infrastructure, I'll
> have
> > to look, I suspect it can cover some cases but not all of them.
> 
> *poke*
> 
> Any update on this?
> 
> Anything I can do to help?

Not yet no. I've looked a bit, but ran out of time, I'll look more this
week-end or next week. I'm also trying to figure out who in IBM is
responsible for that hotplug stuff so they can get involved too.

BTW. How would you do if the answer was we simply can't declare hotplug
"slots" ? ie. if I end up finding out (which is what I think will
happen) that there is simply no way for us to know in advance any
concept of "slot" with a devfn for hotplug ?

Basically, when doing hotplug, the hypervisor sends us new bits of
device-tree with things potentially ranging from host bridges, P2P
bridges to devices, but I'm not certain at this stage we can know in
advance where they'll hook up (in fact, for PHBs, we can't for sure) and
thus even if we end up supporting hotplug of actual slots, we don't even
know in advance the devfn where devices will appear. It's all hidden
from us by the hypervisor.

How would that fit in your infrastructure ? Can we just disable usage of
your slots abstraction in our case ?

Cheers,
Ben.

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