On 4/28/05, Chris Friesen <[email protected]> wrote:
>
> We recently had an issue with a kernel module leaking memory on unload,
> and a userspace app that unloaded it way too many times.
>
> This ended up using up a bunch of memory, which triggered the oom-killer
> to run, which went wild killing everything in sight since userspace
> wasn't actually the culprt.
>
> One idea we had to prevent this in the future is to configure the OOM
> killer to reset the system if the kernel uses more than a certain amount
> of memory. (Reset is better than hang for our purposes.) Is there any
Curiously, how to reset? Reboot? (Teach oom killer to kill) or restart
the related
kernel thread?
> way to find out how much memory the kernel is using? I don't see
> anything in /proc, but maybe something internal that isn't currently
> exported?
>
> Chris
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
