All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Srinivas_G_Gowda@Dell.com
Cc: minyard@acm.org, tcminyard@gmail.com, mjg59@srcf.ucam.org,
	andi@firstfloor.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, 4 Jul 2012 14:17:26 +0200	[thread overview]
Message-ID: <20120704121726.GP11413@one.firstfloor.org> (raw)
In-Reply-To: <4FF3D090.8000403@dell.com>

> The intend of this patch was not to really workaround any issues, the aim was for the management software to use this data. 

.. use it to do something "Linux" specific right?

I think Corey summed it up pretty well in his previous comment. Management software associated with BMC usually use this information to let the users know about the OS that is using the BMC. Generally there are 3rd party application software that goes and pretty much fills up the OS env information and the management software uses this. My intend was why don't we get this information loaded by the driver itself. If there are applications that wants to rewrite it, so be it..! 
> 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 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.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

  reply	other threads:[~2012-07-04 12:17 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 [this message]
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=20120704121726.GP11413@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=Srinivas_G_Gowda@Dell.com \
    --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 \
    --cc=tcminyard@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.