linux-kernel - Re: [PATCH 2/3] ipmi: Only register one si per bmc

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20100421201048.GA25030@srcf.ucam.org>
Date:	Wed, 21 Apr 2010 21:10:48 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Corey Minyard <minyard@....org>
Cc:	openipmi-developer@...ts.sourceforge.net, bjorn.helgaas@...com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] ipmi: Only register one si per bmc

On Wed, Apr 21, 2010 at 03:03:21PM -0500, Corey Minyard wrote:

> However, IBM makes some systems that can plug together for scalability.   
> Each individual system has a BMC, and when you plug them together into  
> an SMP system, all the BMCs are still there.  At least that's how I  
> understand it.  I'm not sure if the other BMCs become satellite MCs in  
> that case, which would be legit, sort of.  So I guess the answer to you  
> question would be: "Yes, the world is not compatible with the spec".

Hm. Ok. In that case we seem to be in a difficult position - we're not 
supposed to register multiple SIs per BMC, but we're also not supposed 
to send anything other than GetDeviceID to an SI before we decide to use 
it. The options here would seem to be to disambiguate by either 
registering all SIs of a type (on the assumption that if we have 
multiple BMCs, they'll all present their SIs in the same way, and we 
won't have multiple SIs of the same type if we don't have multiple 
BMCs), or taking a risk on that bit of the spec by getting the GUID for 
each SI.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/