Date: Fri, 20 Jun 2003 13:06:15 -0400 From: Mike Tancsa <mike@sentex.net> To: ultraviolet@epweb.co.za, freebsd-stable@freebsd.org Subject: Re: Zsh fork bomb paniced my kernel. Message-ID: <5.2.0.9.0.20030620130214.071b0c58@209.112.4.2> In-Reply-To: <20030620155516.GC7055@tulip.epweb.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes and no. It seems that if certain resources get starved bad things will
happen. The OS will let you shoot yourself in the foot afterall. You can
protect yourself from yourself by adjusting the defaults in /etc/login.conf.
---Mike
At 05:55 PM 20/06/2003 +0200, William Fletcher wrote:
>Hi,
>
>My machine just bombed when I did the following stupid command.
>:(){:|:};:
>Zsh chewed up everything on the machine...
>I ran it knowing I'd probably have to reboot.
>
>But, I hardly expected it to panic.
>
>Or, was that normal?
>
>Anyway, the following is some detail...
>Please mail me if there is more I'm ment to do.
>
>Thanks in advance :)
>
>ultraviolet@tulip:~ %> uname -a
>FreeBSD tulip.epweb.co.za 4.8-STABLE FreeBSD 4.8-STABLE #0: Wed Jun 11
>10:09:55
>SAST 2003 root@tulip.epweb.co.za:/usr/src/sys/compile/TULIP i386
>
>Panic message:
>IdlePTD at phsyical address 0x0042a000
>initial pcb at physical address 0x0036e460
>panicstr: vm_map_entry_create: kernel resources exhausted
>initial pcb at physical address 0x0036e460
>panicstr: vm_map_entry_create: kernel resources exhausted
>panic messages:
>---
>panic: vm_map_entry_create: kernel resources exhausted
>
>syncing disks... 2 2
>done
>Uptime: 7d7h13m45s
>
>(kgdb) where
>#0 0xc01682aa in dumpsys ()
>#1 0xc016807b in boot ()
>#2 0xc01684a0 in poweroff_wait ()
>#3 0xc02553f0 in vm_map_entry_create ()
>#4 0xc02555e9 in vm_map_insert ()
>#5 0xc0255810 in vm_map_find ()
>#6 0xc0178cfb in pipespace ()
>#7 0xc0178dd2 in pipe_create ()
>#8 0xc0178b54 in pipe ()
>#9 0xc02c21f5 in syscall2 ()
>#10 0xc02b3875 in Xint0x80_syscall ()
>#11 0x28081e1f in ?? ()
>#12 0x2808135b in ?? ()
>#13 0x28080deb in ?? ()
>#14 0x28080b6e in ?? ()
>#15 0x28086b39 in ?? ()
>#16 0x28086964 in ?? ()
>#17 0x280863fc in ?? ()
>#18 0x2808458a in ?? ()
>#19 0x28081e1f in ?? ()
>#20 0x2808135b in ?? ()
>#21 0x28080deb in ?? ()
>#22 0x28080b6e in ?? ()
>#23 0x28086b39 in ?? ()
>---Type <return> to continue, or q <return> to quit---
>#24 0x28086964 in ?? ()
>#25 0x280863fc in ?? ()
>#26 0x2808458a in ?? ()
>#27 0x28081e1f in ?? ()
>#28 0x2808135b in ?? ()
>#29 0x28080deb in ?? ()
>#30 0x28080b6e in ?? ()
>#31 0x28086b39 in ?? ()
>#32 0x28086964 in ?? ()
>#33 0x280863fc in ?? ()
>#34 0x2808458a in ?? ()
>#35 0x28081e1f in ?? ()
>#36 0x2808135b in ?? ()
>#37 0x28080deb in ?? ()
>#38 0x28080b6e in ?? ()
>#39 0x28086b39 in ?? ()
>#40 0x28086964 in ?? ()
>#41 0x280863fc in ?? ()
>#42 0x2808458a in ?? ()
>Cannot access memory at address 0xbfbfd040.
>
>--
>William Fletcher (ultraviolet) Powered by
>http://www.FreeBSD.org/
>IT Administrator, EPWeb networks.
>http://www.epweb.co.za/
>Tel: +27 (041) 395 6800
>Fax: +27 (041) 395 6818
>Support: support@epweb.co.za
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.2.0.9.0.20030620130214.071b0c58>