linux-kernel - RE: [PATCH][resubmit] HP iLO driver

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:	Tue, 8 Jul 2008 22:19:18 +0000
From:	"Altobelli, David" <david.altobelli@...com>
To:	Pavel Machek <pavel@...e.cz>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"greg@...ah.com" <greg@...ah.com>
Subject: RE: [PATCH][resubmit] HP iLO driver

Pavel Machek wrote:
> Could you provide the list of commands (at least) so we can be more
> concrete?

Unfortunately, I don't believe that I can.  We reviewed this internally,
and the question of documentation was raised.  The hardware teams did
not approve disseminating the ABI.  To be clear, we understand what we
are doing by releasing the driver as GPLv2, the actual functionality
of communicating with iLO was okayed for release.  But releasing the
specifics of what we can send was not approved.

> Yes, I believe we do want to have 30 commands it kernel, because it
> will allow same userland to work on HP machines, AMD machines, etc...

We sell AMD :)

> (I assume management processors have pretty similar functionality
> accross vendors, right?)

I can't speak for other vendors.

>> It seems much cleaner to keep the kernel interface simple and opaque
>> (ie read/write), and handle the details of the commands in user
>> space. From my limited understanding, I thought that was a common
>> goal here: move what you can to userspace.
>
> We are not _that_ extreme. Yes, keep stuff in userspace is important,
> but "hide hardware differences" is more important goal.

That seems like a larger question/goal.  Giving users some consistent
interfaces to do stuff would be nice, but I'd really like to handle this
driver on its own.
--
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/