From: Corey Minyard <tcminyard@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Srinivas_G_Gowda@Dell.com, tcminyard@gmail.com,
mjg59@srcf.ucam.org, linux-kernel@vger.kernel.org,
openipmi-developer@lists.sourceforge.net, jharg93@gmail.com
Subject: Re: [PATCH 1/1 v2 ] ipmi: Setting OS name as Linux in BMC
Date: Wed, 04 Jul 2012 12:41:13 -0500 [thread overview]
Message-ID: <4FF48039.3020505@acm.org> (raw)
In-Reply-To: <20120704121726.GP11413@one.firstfloor.org>
On 07/04/2012 07:17 AM, Andi Kleen wrote:
>> Rather than just have a static entry such as 'Linux' I could probably write the version number and more(distro name etc.. )
>>
>> Thoughts.. ?
> I still think "Linux" means nothing even to the management software.
> What should it do with that?
>
> If you provide some way for a distro to fill in "foobar linux 1.2.3.4"
> maybe. But just Linux or even Linux x.y.z would be wrong because the same kernel
> version can behave very differently.
>
> But it would be better to define specific feature flags for
> specific needs that actually mean something.
I think the conclusion I have come to is that this really belongs as a
small program that runs at startup. That's not significantly different
than having it done in the driver. I can help you write it, if you like.
I think Andi is right here. "Linux" may mean something to your
management software. Some other management software may want "Linux
x.y.z". Another may want "SuSE Enterprise Linux x.y". It's impossible
to be general enough in the kernel.
>
>> I know there were some concerns with the security aspect, Can you please let me know what kind of security holes we could be looking at ?
> I don't think there are any security problems. just forward/backward
> compatibility problems, as the ACPI experience shows.
I had mentioned possible security issues with having some daemon that
identified the system directly over IP. I don't think there are any
issues with IPMI, at least not any more than you already have with IPMI,
and it's reasonably secure for what it does.
-corey
prev parent reply other threads:[~2012-07-04 17:41 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
2012-07-04 5:11 ` Srinivas_G_Gowda
2012-07-04 12:17 ` Andi Kleen
2012-07-04 17:41 ` Corey Minyard [this message]
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=4FF48039.3020505@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).