From: Corey Minyard <tcminyard@gmail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Andi Kleen <andi@firstfloor.org>,
Srinivas_G_Gowda@Dell.com, tcminyard@gmail.com,
linux-kernel@vger.kernel.org,
"openipmi-developer@lists.sourceforge.net"
<openipmi-developer@lists.sourceforge.net>,
jharg93@gmail.com
Subject: Re: [PATCH 1/1 v2 ] ipmi: Setting OS name as Linux in BMC
Date: Fri, 29 Jun 2012 09:27:08 -0500 [thread overview]
Message-ID: <4FEDBB3C.7080105@acm.org> (raw)
In-Reply-To: <20120629123001.GA26545@srcf.ucam.org>
On 06/29/2012 07:30 AM, Matthew Garrett wrote:
> On Thu, Jun 28, 2012 at 05:01:54PM -0700, Andi Kleen wrote:
>> Not sure that's all that useful. I can just see BMC's making the ACPI
>> mistake of trying to work around specific issues, by checking for
>> Linux.
I'm not sure I see that happening, but I suppose you never know.
>>
>> But since there are so many different Linux that will never work
>> because "Linux" does not describe a fixed release or code base.
>>
>> Probably dangerous.
> Agreed. Linux doesn't make interface guarantees to hardware, and where
> we've implied that we do it's ended up breaking things.
>
This is not really about making interface guarantees to hardware. This
is more of a management discovery thing, so that system management
software talking to the BMC can know what is running on the target.
Something where management software can say "Hey, why is Linux running
on that box? It's supposed to be BSD." or "That box has booted Linux but
hasn't started its maintenance software". According to the spec, the
information is supposed to be cleared if the system powers down or resets.
It seems to me that it's better to directly query what is running on the
target to know what is running on it, but perhaps that's a security
problem waiting to happen. And perhaps it's better to have a small
program set this at startup, since this operation will currently fail on
the majority of systems out there.
-corey
next prev parent reply other threads:[~2012-06-29 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FEC8931.5020001@dell.com>
2012-06-28 16:45 ` [PATCH 1/1 v2 ] ipmi: Setting OS name as Linux in BMC Srinivas_G_Gowda
2012-06-29 0:01 ` Andi Kleen
2012-06-29 3:06 ` Corey Minyard
2012-06-29 12:30 ` Matthew Garrett
2012-06-29 14:27 ` Corey Minyard [this message]
2012-07-04 5:11 ` Srinivas_G_Gowda
2012-07-04 12:17 ` Andi Kleen
2012-07-04 17:41 ` Corey Minyard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FEDBB3C.7080105@acm.org \
--to=tcminyard@gmail.com \
--cc=Srinivas_G_Gowda@Dell.com \
--cc=andi@firstfloor.org \
--cc=jharg93@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=mjg59@srcf.ucam.org \
--cc=openipmi-developer@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).