Thanks for the report.
However, this is not a bug in GNU ls.
You can get the same effect by repeatedly calling `malloc' directly.
Doing it via `ls' just makes the process take longer.
James Holdsworth <[EMAIL PROTECTED]> writes:
| Morning,
|
| I recently discovered that a local user could compile a short program
| (ow.c) that would when run sucessfully grind a GNU fileutils system to a
| complete halt. I have tried this program on Redhat 6.1 & 6.2 and both
| come down the same way.
|
| It apparantly takes advantage of the way ls -w doesn't check for bounds
| and will allocate memory until it is exhausted.
|
| I am running Redhat 6.1 (Kernel 2.2.16-3smp), with version 4.0p of (ls -
| fileutils). I also attach the offending code I tracked down from
| rootshell.com.
|
| --
| System Admin - h66md.dyndns.org
| Redhat Linux 6.1 [2.2.16-3smp]
