From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+w=401wt.eu-S1755806AbYAXTJs@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1755806AbYAXTJs (ORCPT <rfc822;w@1wt.eu>);
	Thu, 24 Jan 2008 14:09:48 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752313AbYAXTJi
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Thu, 24 Jan 2008 14:09:38 -0500
Received: from gw.goop.org ([64.81.55.164]:39176 "EHLO mail.goop.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752279AbYAXTJh (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Thu, 24 Jan 2008 14:09:37 -0500
Message-ID: <4798E26D.6010908@goop.org>
Date: Thu, 24 Jan 2008 11:09:33 -0800
From: Jeremy Fitzhardinge <jeremy@goop.org>
User-Agent: Thunderbird 2.0.0.9 (X11/20071115)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Oliver_Pinter_=28Pint=E9r_Oliv=E9r=29=22?= 
	<oliver.pntr@gmail.com>
CC: Adrian Bunk <bunk@kernel.org>, David Miller <davem@davemloft.net>,
       Greg KH <gregkh@suse.de>, Greg KH <greg@kroah.com>,
       Linus Torvalds <torvalds@linux-foundation.org>,
       Linux Kernel <linux-kernel@vger.kernel.org>,
       Andrew Morton <akpm@linux-foundation.org>,
       Randy Dunlap <randy.dunlap@oracle.com>,
       Al Viro <viro@zeniv.linux.org.uk>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: Add common orderly_poweroff() to 2.6.22?
References: <6101e8c40801210959v1e0f6e55w26187dc93a09a202@mail.gmail.com>	 <4798C817.6020702@goop.org> <6101e8c40801241033m7347ec5fof8e41c3fe7974feb@mail.gmail.com>
In-Reply-To: <6101e8c40801241033m7347ec5fof8e41c3fe7974feb@mail.gmail.com>
X-Enigmail-Version: 0.95.6
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Oliver Pinter (Pintér Olivér) wrote:
> On 1/24/08, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>   
>> Oliver Pinter (Pintér Olivér) wrote:
>>     
>>> Hi all!
>>>
>>> commit in mainline 10a0a8d4e3f6bf2d077f94344441909abe670f5a is go in
>>> the satble 2.6.22
>>>
>>> the grund for this question is http://hup.hu/node/49773 .
>>>
>>>       
>> Is there a compelling reason?
>>     
>
> no, but in forum some person have the question, why the kernel call
> userspace program and it is secure or not...
>   

Ah, my non-existent knowledge of Hungarian wasn't up to interpreting 
that page ;)

It should be secure if done properly.  Of course, if you set the 
"poweroff" executable to something untrustworthy then you'll have a 
problem, but there's no inherent security problem there.  And if you 
want to do an orderly shutdown, you need to have some amount of help 
from the userspace side of things, and invoking a command is the normal 
way to do this.

    J