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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20100421182154.GA16436@srcf.ucam.org>
Date:	Wed, 21 Apr 2010 19:21:54 +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 01:09:45PM -0500, Corey Minyard wrote:

> If I understand this correctly, this would really be "Only register one  
> si per system".  Unfortunately, there are systems that have more than  
> one BMC each with their own interface.

The spec explicitly says that while a system may have multiple BMCs, 
only one BMC may respond to GetDeviceID (6.11 of the 2.0 spec). Is the 
real world irritatingly incompatible with this?

> Also, I believe the driver would not function between the previous 
> patch and this patch, which isn't the best.

That's true. I can fix that up fairly easily.

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