From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "\"Oliver Pinter (Pintér Olivér)\"" <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?
Date: Thu, 24 Jan 2008 11:09:33 -0800 [thread overview]
Message-ID: <4798E26D.6010908@goop.org> (raw)
In-Reply-To: <6101e8c40801241033m7347ec5fof8e41c3fe7974feb@mail.gmail.com>
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
next prev parent reply other threads:[~2008-01-24 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 17:59 Add common orderly_poweroff() to 2.6.22? Oliver Pinter (Pintér Olivér)
2008-01-24 17:17 ` Jeremy Fitzhardinge
2008-01-24 18:33 ` Oliver Pinter (Pintér Olivér)
2008-01-24 19:09 ` Jeremy Fitzhardinge [this message]
2008-01-24 20:28 ` Oliver Pinter (Pintér Olivér)
2008-01-24 21:12 ` Jeremy Fitzhardinge
2008-01-24 21:35 ` Oliver Pinter (Pintér Olivér)
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=4798E26D.6010908@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.pntr@gmail.com \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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