mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Mielke <mark@mark.mielke.cc>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: James Stevenson <james@stev.org>, pd dd <parviz_kernel@yahoo.com>,
	"M. Soltysiak" <msoltysiak@hotmail.com>,
	ML-linux-kernel <linux-kernel@vger.kernel.org>,
	William Stearns <wstearns@pobox.com>
Subject: Re: Linux BUG: Memory Leak
Date: Thu, 13 Mar 2003 10:10:47 -0500	[thread overview]
Message-ID: <20030313151047.GA20516@mark.mielke.cc> (raw)
In-Reply-To: <Pine.LNX.3.95.1030313093618.21484A-100000@chaos>

On Thu, Mar 13, 2003 at 09:42:39AM -0500, Richard B. Johnson wrote:
> But it's a memory leak in the game, not the kernel. They should
> complain to the game makers. If a game runs the system out of
> memory so a user can't log in on the root account and kill off
> the game, it's a problem with the game.

I would like to encourage the camp of people who believe that UNIX can
be a stable server platform to innovate ways of ensuring that if a game
(or other memory intensive program) does run the system out of memory,
an administrator could login as root and kill the game.

So I don't agree with your conclusion. I think "your system crashed? well
contact the application designer..." is a mindset that was strongly
encoduraged by companies such as Microsoft, as it allowed them to release
half baked kernels and call them stable. Thankfully, even Microsoft has
learned that this isn't the best approach, and WinXP is quite a deal more
solid than Win95.

Yes, Linux is the result of (mostly) volunteer effort contributed to the
community. No, I don't think that means it is acceptable for it to contain
security exploits, or for it to be any less robust than other operating
systems in its class such as AIX or Solaris. We have smart people. Let's
use them. Let's not be satisfied with less.

mark

-- 
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
.  .  _  ._  . .   .__    .  . ._. .__ .   . . .__  | Neighbourhood Coder
|\/| |_| |_| |/    |_     |\/|  |  |_  |   |/  |_   | 
|  | | | | \ | \   |__ .  |  | .|. |__ |__ | \ |__  | Ottawa, Ontario, Canada

  One ring to rule them all, one ring to find them, one ring to bring them all
                       and in the darkness bind them...

                           http://mark.mielke.cc/


  reply	other threads:[~2003-03-13 14:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12  6:49 M. Soltysiak
2003-03-12  7:19 ` David Shirley
2003-03-12 10:04   ` Maciej Soltysiak
2003-03-12 18:38   ` James Stevenson
2003-03-12 19:25     ` Elladan
2003-03-12  7:22 ` Mike Galbraith
2003-03-12  7:30 ` William Stearns
2003-03-13  7:13   ` William Stearns
2003-03-13  9:13     ` pd dd
2003-03-13 14:26       ` James Stevenson
2003-03-13 15:45         ` Alan Cox
2003-03-13 15:05           ` Tomas Szepe
2003-03-13 15:33             ` Damian Kołkowski
2003-03-13 16:29             ` venom
2003-03-13 14:26       ` James Stevenson
2003-03-13 14:42         ` Richard B. Johnson
2003-03-13 15:10           ` Mark Mielke [this message]
2003-03-13 15:13             ` Richard B. Johnson
2003-03-13 18:54             ` Alan Cox
2003-03-13 15:06         ` Martin Schlemmer
2003-03-13 14:27       ` James Stevenson
2003-03-13 15:43         ` Alan Cox
2003-03-12 16:49 ` Disconnect
2003-03-12 19:24 Felipe Alfaro Solana
2003-03-12 20:58 ` James Stevenson
2003-03-12 22:23 Felipe Alfaro Solana

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=20030313151047.GA20516@mark.mielke.cc \
    --to=mark@mark.mielke.cc \
    --cc=james@stev.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msoltysiak@hotmail.com \
    --cc=parviz_kernel@yahoo.com \
    --cc=root@chaos.analogic.com \
    --cc=wstearns@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®