All of lore.kernel.org
 help / color / mirror / Atom feed
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 13:12:50 -0800	[thread overview]
Message-ID: <4798FF52.30801@goop.org> (raw)
In-Reply-To: <6101e8c40801241228m6026b91bnfcf29c2da3944dfa@mail.gmail.com>

Oliver Pinter (Pintér Olivér) wrote:
> the original topic name is : why linux kernel crap ...
>
> the substance is, when from kernel call users-pace program, then come
> up more problems with security...
> when the fs crash out or the userspace code is breaked, then the
> system not shuting down ..
>   

orderly_poweroff() has the option to force a hard shutdown if the exec 
of the usermode command fails.

    J

  reply	other threads:[~2008-01-24 21:13 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
2008-01-24 20:28       ` Oliver Pinter (Pintér Olivér)
2008-01-24 21:12         ` Jeremy Fitzhardinge [this message]
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=4798FF52.30801@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 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.