From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Pavel Machek <pavel@suse.cz>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Bulent Abali <abali@us.ibm.com>,
"Dirk W. Steinberg" <dws@dirksteinberg.de>,
Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Swapping for diskless nodes
Date: Tue, 14 Aug 2001 13:57:54 +0100 (BST) [thread overview]
Message-ID: <E15Wdla-00018V-00@the-village.bc.nu> (raw)
In-Reply-To: <20010811011329.C55@toy.ucw.cz> from "Pavel Machek" at Aug 11, 2001 01:13:29 AM
> > Ultimately its an insoluble problem, neither SunOS, Solaris or NetBSD are
> > infallible, they just never fail for any normal situation, and thats good
> > enough for me as a solution
>
> Oops, really? And if I can DoS such machine with ping -f (to eat atomic
> ram)? And what are you going to tel your users? "It died so reboot"?
For the simplistic case you can stop queueing data to user sockets but that
isnt neccessarily a cure - it can lead to bogus OOM by preventing progress
of apps that would otherwise read a packet then exit.
The good example of the insoluble end of it is a box with no default route
doing BGP4 routing with NFS swap. Now thats an extremely daft practical
proposition but it illustrates the fact the priority ordering is not known
to the kernel
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2001-08-14 12:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 14:26 Bulent Abali
2001-08-09 15:13 ` Alan Cox
2001-08-09 20:57 ` Rik van Riel
2001-08-09 22:46 ` Alan Cox
2001-08-11 1:16 ` Pavel Machek
2001-08-11 1:13 ` Pavel Machek
2001-08-14 12:57 ` Alan Cox [this message]
2001-08-16 21:46 ` Pavel Machek
2001-08-17 0:46 ` Rik van Riel
2001-08-17 1:35 ` Jakob Østergaard
2001-08-17 21:23 ` Pavel Machek
2001-08-17 6:42 ` Andreas Haumer
2001-08-17 21:25 ` Pavel Machek
2001-08-17 21:03 ` Andreas Haumer
2001-08-17 22:31 ` Dirk W. Steinberg
[not found] <no.id>
[not found] ` <E15Ulnx-0006zZ-00@the-village.bc.nu>
2001-08-09 10:50 ` Ingo Oeser
2001-08-09 13:12 ` Dirk W. Steinberg
2001-08-09 20:47 ` Rik van Riel
2001-08-09 15:19 ` Alan Cox
2001-08-09 17:09 ` Eric W. Biederman
2001-08-09 20:58 ` Rik van Riel
2001-08-10 8:11 ` Eric W. Biederman
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=E15Wdla-00018V-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=abali@us.ibm.com \
--cc=dws@dirksteinberg.de \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pavel@suse.cz \
/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